Eric Biggers a5d431eff2 fscrypt: make fscrypt_operations.key_prefix a string ... There was an unnecessary amount of complexity around requesting the filesystem-specific key prefix. It was unclear why; perhaps it was envisioned that different instances of the same filesystem type could use different key prefixes, or that key prefixes could be binary. However, neither of those things were implemented or really make sense at all. So simplify the code by making key_prefix a const char *. Signed-off-by: Eric Biggers <ebiggers@google.com> Reviewed-by: Richard Weinberger <richard@nod.at> Signed-off-by: Theodore Ts'o <tytso@mit.edu>		2017-01-08 01:03:41 -05:00
..
bio.c	fscrypt: factor out bio specific functions	2017-01-01 16:18:49 -05:00
crypto.c	fscrypt: factor out bio specific functions	2017-01-01 16:18:49 -05:00
fname.c	fscrypt: use ENOKEY when file cannot be created w/o key	2016-12-31 16:26:20 -05:00
fscrypt_private.h	fscrypt: factor out bio specific functions	2017-01-01 16:18:49 -05:00
Kconfig	fscrypt: factor out bio specific functions	2017-01-01 16:18:49 -05:00
keyinfo.c	fscrypt: make fscrypt_operations.key_prefix a string	2017-01-08 01:03:41 -05:00
Makefile	fscrypt: factor out bio specific functions	2017-01-01 16:18:49 -05:00
policy.c	fscrypt: make test_dummy_encryption require a keyring key	2017-01-02 15:39:46 -05:00