f2fs: go out for insert_inode_locked failure

We should not call unlock_new_inode when insert_inode_locked failed.

Reviewed-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

1 files changed, 1 insertions, 4 deletions

diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
index 97e97c41b979..a680bf38e4f0 100644
--- a/fs/f2fs/namei.c
+++ b/fs/f2fs/namei.c
@@ -53,7 +53,7 @@ static struct inode *f2fs_new_inode(struct inode *dir, umode_t mode)
         if (err) {
                 err = -EINVAL;
                 nid_free = true;
-                goto out;
+                goto fail;
         }
 
         /* If the directory encrypted, then we should encrypt the inode. */
@@ -75,9 +75,6 @@ static struct inode *f2fs_new_inode(struct inode *dir, umode_t mode)
         mark_inode_dirty(inode);
         return inode;
 
-out:
-        clear_nlink(inode);
-        unlock_new_inode(inode);
 fail:
         trace_f2fs_new_inode(inode, err);
         make_bad_inode(inode);