diff options
author | Eric Biggers <ebiggers@google.com> | 2020-12-02 18:20:37 -0800 |
---|---|---|
committer | Eric Biggers <ebiggers@google.com> | 2020-12-02 18:25:01 -0800 |
commit | ec0caa974cd092549ab282deb8ec7ea73b36eba0 (patch) | |
tree | 9609384a2e6542df8862a9f2d903e62dbc4e10c8 /fs/ext4/dir.c | |
parent | 91d0d89241b4201d612bfac623199c84363286e9 (diff) | |
download | linux-stable-ec0caa974cd092549ab282deb8ec7ea73b36eba0.tar.gz linux-stable-ec0caa974cd092549ab282deb8ec7ea73b36eba0.tar.bz2 linux-stable-ec0caa974cd092549ab282deb8ec7ea73b36eba0.zip |
fscrypt: introduce fscrypt_prepare_readdir()
The last remaining use of fscrypt_get_encryption_info() from filesystems
is for readdir (->iterate_shared()). Every other call is now in
fs/crypto/ as part of some other higher-level operation.
We need to add a new argument to fscrypt_get_encryption_info() to
indicate whether the encryption policy is allowed to be unrecognized or
not. Doing this is easier if we can work with high-level operations
rather than direct filesystem use of fscrypt_get_encryption_info().
So add a function fscrypt_prepare_readdir() which wraps the call to
fscrypt_get_encryption_info() for the readdir use case.
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Link: https://lore.kernel.org/r/20201203022041.230976-6-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
Diffstat (limited to 'fs/ext4/dir.c')
-rw-r--r-- | fs/ext4/dir.c | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/fs/ext4/dir.c b/fs/ext4/dir.c index 16bfbdd5007c..c6d16353326a 100644 --- a/fs/ext4/dir.c +++ b/fs/ext4/dir.c @@ -118,11 +118,9 @@ static int ext4_readdir(struct file *file, struct dir_context *ctx) struct buffer_head *bh = NULL; struct fscrypt_str fstr = FSTR_INIT(NULL, 0); - if (IS_ENCRYPTED(inode)) { - err = fscrypt_get_encryption_info(inode); - if (err) - return err; - } + err = fscrypt_prepare_readdir(inode); + if (err) + return err; if (is_dx_dir(inode)) { err = ext4_dx_readdir(file, ctx); |