fscrypt: Have filesystems handle their d_ops
This shifts the responsibility of setting up dentry operations from fscrypt to the individual filesystems, allowing them to have their own operations while still setting fscrypt's d_revalidate as appropriate. Most filesystems can just use generic_set_encrypted_ci_d_ops, unless they have their own specific dentry operations as well. That operation will set the minimal d_ops required under the circumstances. Since the fscrypt d_ops are set later on, we must set all d_ops there, since we cannot adjust those later on. This should not result in any change in behavior. Signed-off-by:Daniel Rosenberg <drosen@google.com> Acked-by:
Theodore Ts'o <tytso@mit.edu> Acked-by:
Eric Biggers <ebiggers@google.com> Signed-off-by:
Jaegeuk Kim <jaegeuk@kernel.org>
Showing
- fs/crypto/fname.c 0 additions, 4 deletionsfs/crypto/fname.c
- fs/crypto/fscrypt_private.h 0 additions, 1 deletionfs/crypto/fscrypt_private.h
- fs/crypto/hooks.c 0 additions, 1 deletionfs/crypto/hooks.c
- fs/ext4/dir.c 0 additions, 7 deletionsfs/ext4/dir.c
- fs/ext4/ext4.h 0 additions, 4 deletionsfs/ext4/ext4.h
- fs/ext4/namei.c 1 addition, 0 deletionsfs/ext4/namei.c
- fs/ext4/super.c 0 additions, 5 deletionsfs/ext4/super.c
- fs/f2fs/dir.c 0 additions, 7 deletionsfs/f2fs/dir.c
- fs/f2fs/f2fs.h 0 additions, 3 deletionsfs/f2fs/f2fs.h
- fs/f2fs/namei.c 1 addition, 0 deletionsfs/f2fs/namei.c
- fs/f2fs/super.c 0 additions, 1 deletionfs/f2fs/super.c
- fs/ubifs/dir.c 1 addition, 0 deletionsfs/ubifs/dir.c
- include/linux/fscrypt.h 5 additions, 2 deletionsinclude/linux/fscrypt.h
Loading
Please register or sign in to comment