Messages in this thread Patch in this message | | | From | Chao Yu <> | Subject | [PATCH] f2fs: don't call fscrypt_get_encryption_info() explicitly in f2fs_tmpfile() | Date | Sat, 21 Mar 2020 20:23:27 +0800 |
| |
From: Chao Yu <yuchao0@huawei.com>
In f2fs_tmpfile(), parent inode's encryption info is only used when inheriting encryption context to its child inode, however, we have already called fscrypt_get_encryption_info() in fscrypt_inherit_context() to get the encryption info, so just removing unneeded one in f2fs_tmpfile().
Signed-off-by: Chao Yu <yuchao0@huawei.com> --- fs/f2fs/namei.c | 6 ------ 1 file changed, 6 deletions(-)
diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c index 95cfbce062e8..f54119da2217 100644 --- a/fs/f2fs/namei.c +++ b/fs/f2fs/namei.c @@ -874,12 +874,6 @@ static int f2fs_tmpfile(struct inode *dir, struct dentry *dentry, umode_t mode) if (!f2fs_is_checkpoint_ready(sbi)) return -ENOSPC; - if (IS_ENCRYPTED(dir) || DUMMY_ENCRYPTION_ENABLED(sbi)) { - int err = fscrypt_get_encryption_info(dir); - if (err) - return err; - } - return __f2fs_tmpfile(dir, dentry, mode, NULL); } -- 2.22.0
| |