diff options
author | Eric Biggers <ebiggers@google.com> | 2019-03-20 11:39:11 -0700 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2019-04-17 10:05:51 -0400 |
commit | 0bf3d5c1604ecbbd4e49e9f5b3c79152b87adb0d (patch) | |
tree | 97a5f5cedec9b310490df829e03997036869c9fa /net/l3mdev | |
parent | 968dd6d0c6d6b6a989c6ddb9e2584a031b83e7b5 (diff) | |
download | linux-0bf3d5c1604ecbbd4e49e9f5b3c79152b87adb0d.tar.gz linux-0bf3d5c1604ecbbd4e49e9f5b3c79152b87adb0d.tar.bz2 linux-0bf3d5c1604ecbbd4e49e9f5b3c79152b87adb0d.zip |
fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory
Make __d_move() clear DCACHE_ENCRYPTED_NAME on the source dentry. This
is needed for when d_splice_alias() moves a directory's encrypted alias
to its decrypted alias as a result of the encryption key being added.
Otherwise, the decrypted alias will incorrectly be invalidated on the
next lookup, causing problems such as unmounting a mount the user just
mount()ed there.
Note that we don't have to support arbitrary moves of this flag because
fscrypt doesn't allow dentries with DCACHE_ENCRYPTED_NAME to be the
source or target of a rename().
Fixes: 28b4c263961c ("ext4 crypto: revalidate dentry after adding or removing the key")
Reported-by: Sarthak Kukreti <sarthakkukreti@chromium.org>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'net/l3mdev')
0 files changed, 0 insertions, 0 deletions