f2fs: avoid opened loop codes in __add_ino_entry
authorChao Yu <yuchao0@huawei.com>
Fri, 10 Nov 2017 01:30:42 +0000 (09:30 +0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Tue, 19 Dec 2017 03:39:11 +0000 (19:39 -0800)
commiteb84a567f686f1da5e669a3000f725b66a40ce21
tree11aa81760d173f6a0cd0fe5f08977afba7dcf674
parent793cdb935708dbda3c2ce7ce96ade2c8e94d44c2
f2fs: avoid opened loop codes in __add_ino_entry

We will keep __add_ino_entry success all the time, for ENOMEM failure
case, we have already handled it by using  __GFP_NOFAIL flag, so we
don't have to use additional opened loop codes here, remove them.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/checkpoint.c