summaryrefslogtreecommitdiffstats
path: root/fs/f2fs/inline.c
diff options
context:
space:
mode:
authorKinglong Mee <kinglongmee@gmail.com>2017-03-10 16:28:46 +0800
committerJaegeuk Kim <jaegeuk@kernel.org>2017-03-21 22:34:33 -0400
commitd03ba4cc3fa639916a86b61c5a3d817cb6aa91a0 (patch)
tree65d15f6dbdaf2f527e8ae3fce3947317c0afb137 /fs/f2fs/inline.c
parent346fe752c431bcef5d05614263a4b4a0cfe88e10 (diff)
downloadlinux-stable-d03ba4cc3fa639916a86b61c5a3d817cb6aa91a0.tar.gz
linux-stable-d03ba4cc3fa639916a86b61c5a3d817cb6aa91a0.tar.bz2
linux-stable-d03ba4cc3fa639916a86b61c5a3d817cb6aa91a0.zip
f2fs: cleanup the disk level filename updating
As discuss with Jaegeuk and Chao, "Once checkpoint is done, f2fs doesn't need to update there-in filename at all." The disk-level filename is used only one case, 1. create a file A under a dir 2. sync A 3. godown 4. umount 5. mount (roll_forward) Only the rename/cross_rename changes the filename, if it happens, a. between step 1 and 2, the sync A will caused checkpoint, so that, the roll_forward at step 5 never happens. b. after step 2, the roll_forward happens, file A will roll forward to the result as after step 1. So that, any updating the disk filename is useless, just cleanup it. Signed-off-by: Kinglong Mee <kinglongmee@gmail.com> Reviewed-by: Chao Yu <yuchao0@huawei.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/inline.c')
-rw-r--r--fs/f2fs/inline.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/f2fs/inline.c b/fs/f2fs/inline.c
index 93c15337bcd9..701bbd8d10ba 100644
--- a/fs/f2fs/inline.c
+++ b/fs/f2fs/inline.c
@@ -528,8 +528,6 @@ int f2fs_add_inline_entry(struct inode *dir, const struct qstr *new_name,
err = PTR_ERR(page);
goto fail;
}
- if (f2fs_encrypted_inode(dir))
- file_set_enc_name(inode);
}
f2fs_wait_on_page_writeback(ipage, NODE, true);