diff options
| author | Jaegeuk Kim <jaegeuk@kernel.org> | 2015-05-06 18:23:21 -0700 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2015-05-28 15:41:57 -0700 |
| commit | d690358b2bf43f5cb12ce07d209d09b1decb79c3 (patch) | |
| tree | 011edc598aad4c27128e5750fd213487c8ccc148 /fs/f2fs/namei.c | |
| parent | edf3fb8e9e5771944815fadbd8ef6a7e43ef0f7c (diff) | |
| download | op-kernel-dev-d690358b2bf43f5cb12ce07d209d09b1decb79c3.zip op-kernel-dev-d690358b2bf43f5cb12ce07d209d09b1decb79c3.tar.gz | |
f2fs crypto: remove checking key context during lookup
No matter what the key is valid or not, readdir shows the dir entries correctly.
So, lookup should not failed.
But, we expect further accesses should be denied from open, rename, link, and so
on.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/namei.c')
| -rw-r--r-- | fs/f2fs/namei.c | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c index bbd83e4..4ad7242 100644 --- a/fs/f2fs/namei.c +++ b/fs/f2fs/namei.c @@ -260,16 +260,6 @@ static struct dentry *f2fs_lookup(struct inode *dir, struct dentry *dentry, if (IS_ERR(inode)) return ERR_CAST(inode); - if (f2fs_encrypted_inode(dir) && f2fs_may_encrypt(inode) && - !f2fs_is_child_context_consistent_with_parent(dir, inode)) { - iput(inode); - f2fs_msg(inode->i_sb, KERN_WARNING, - "Inconsistent encryption contexts: %lu/%lu\n", - (unsigned long)dir->i_ino, - (unsigned long)inode->i_ino); - return ERR_PTR(-EPERM); - } - if (f2fs_has_inline_dots(inode)) { err = __recover_dot_dentries(inode, dir->i_ino); if (err) |
