linux/fs/crypto
Eric Biggers 94840e3c80 fscrypt: eliminate ->prepare_context() operation
The only use of the ->prepare_context() fscrypt operation was to allow
ext4 to evict inline data from the inode before ->set_context().
However, there is no reason why this cannot be done as simply the first
step in ->set_context(), and in fact it makes more sense to do it that
way because then the policy modes and flags get validated before any
real work is done.  Therefore, merge ext4_prepare_context() into
ext4_set_context(), and remove ->prepare_context().

Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2017-03-15 14:15:47 -04:00
..
bio.c fscrypt: factor out bio specific functions 2017-01-01 16:18:49 -05:00
crypto.c fscrypt: remove broken support for detecting keyring key revocation 2017-03-15 13:12:05 -04:00
fname.c fscrypt: remove broken support for detecting keyring key revocation 2017-03-15 13:12:05 -04:00
fscrypt_private.h fscrypt: remove broken support for detecting keyring key revocation 2017-03-15 13:12:05 -04:00
Kconfig fscrypt: factor out bio specific functions 2017-01-01 16:18:49 -05:00
keyinfo.c fscrypt: remove broken support for detecting keyring key revocation 2017-03-15 13:12:05 -04:00
Makefile fscrypt: factor out bio specific functions 2017-01-01 16:18:49 -05:00
policy.c fscrypt: eliminate ->prepare_context() operation 2017-03-15 14:15:47 -04:00