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
..
acl.c
acl.h
balloc.c
bitmap.c
block_validity.c
dir.c
ext4_extents.h
ext4_jbd2.c
ext4_jbd2.h
ext4.h	fscrypt: make fscrypt_operations.key_prefix a string	2017-01-08 01:03:41 -05:00
extents_status.c
extents_status.h
extents.c
file.c
fsync.c
hash.c
ialloc.c	fscrypt: use ENOKEY when file cannot be created w/o key	2016-12-31 16:26:20 -05:00
indirect.c
inline.c
inode.c
ioctl.c
Kconfig
Makefile
mballoc.c
mballoc.h
migrate.c
mmp.c
move_extent.c
namei.c	ext4: don't allow encrypted operations without keys	2017-01-08 00:58:23 -05:00
page-io.c
readpage.c
resize.c
super.c	fscrypt: make fscrypt_operations.key_prefix a string	2017-01-08 01:03:41 -05:00
symlink.c
sysfs.c
truncate.h
xattr_security.c
xattr_trusted.c
xattr_user.c
xattr.c
xattr.h