aboutsummaryrefslogtreecommitdiff
path: root/include/linux/fscrypt_common.h
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2017-02-22 13:25:14 -0800
committerMoyster <oysterized@gmail.com>2017-05-21 18:45:06 +0200
commitf6243676342f5a02713ff8215975b3d51c8e052d (patch)
tree3ada83bad40cdf70cefd6e04e555e454102adf18 /include/linux/fscrypt_common.h
parent096f034ea8f9975a5e2304b622bb3e62819ac48a (diff)
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> Conflicts: fs/ext4/super.c
Diffstat (limited to 'include/linux/fscrypt_common.h')
-rw-r--r--include/linux/fscrypt_common.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/linux/fscrypt_common.h b/include/linux/fscrypt_common.h
index 547f81592..10c1abfba 100644
--- a/include/linux/fscrypt_common.h
+++ b/include/linux/fscrypt_common.h
@@ -87,7 +87,6 @@ struct fscrypt_operations {
unsigned int flags;
const char *key_prefix;
int (*get_context)(struct inode *, void *, size_t);
- int (*prepare_context)(struct inode *);
int (*set_context)(struct inode *, const void *, size_t, void *);
int (*dummy_context)(struct inode *);
bool (*is_encrypted)(struct inode *);