Eric Biggers 29a98c1caf fscrypt: use ENOPKG when crypto API support missing ... Return ENOPKG rather than ENOENT when trying to open a file that's encrypted using algorithms not available in the kernel's crypto API. This avoids an ambiguity, since ENOENT is also returned when the file doesn't exist. Note: this is the same approach I'm taking for fs-verity. Signed-off-by: Eric Biggers <ebiggers@google.com>		2019-08-12 19:04:44 -07:00
..
bio.c	fscrypt: decrypt only the needed blocks in __fscrypt_decrypt_bio()	2019-05-28 10:27:53 -07:00
crypto.c	fscrypt: make fscrypt_msg() take inode instead of super_block	2019-08-12 19:04:44 -07:00
fname.c	fscrypt: make fscrypt_msg() take inode instead of super_block	2019-08-12 19:04:44 -07:00
fscrypt_private.h	fscrypt: make fscrypt_msg() take inode instead of super_block	2019-08-12 19:04:44 -07:00
hooks.c	fscrypt: make fscrypt_msg() take inode instead of super_block	2019-08-12 19:04:44 -07:00
Kconfig	fscrypt: remove selection of CONFIG_CRYPTO_SHA256	2019-06-27 10:29:33 -07:00
keyinfo.c	fscrypt: use ENOPKG when crypto API support missing	2019-08-12 19:04:44 -07:00
Makefile	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00
policy.c	fscrypt: don't set policy for a dead directory	2019-05-28 10:48:23 -07:00