Eric Biggers 1058ef0dcb fscrypt: remove CRYPTO_CTR dependency ... fscrypt doesn't use the CTR mode of operation for anything, so there's no need to select CRYPTO_CTR. It was added by commit 71dea01ea2 ("ext4 crypto: require CONFIG_CRYPTO_CTR if ext4 encryption is enabled"). But, I've been unable to identify the arm64 crypto bug it was supposedly working around. I suspect the issue was seen only on some old Android device kernel (circa 3.10?). So if the fix wasn't mistaken, the real bug is probably already fixed. Or maybe it was actually a bug in a non-upstream crypto driver. So, remove the dependency. If it turns out there's actually still a bug, we'll fix it properly. Signed-off-by: Eric Biggers <ebiggers@google.com>		2019-01-23 23:56:43 -05:00
..
bio.c	fscrypt: allow synchronous bio decryption	2018-05-02 14:30:57 -07:00
crypto.c	fscrypt: add Adiantum support	2019-01-06 08:36:21 -05:00
fname.c	fscrypt: add Adiantum support	2019-01-06 08:36:21 -05:00
fscrypt_private.h	fscrypt: add Adiantum support	2019-01-06 08:36:21 -05:00
hooks.c	fscrypt: use a common logging function	2018-05-20 16:21:05 -04:00
Kconfig	fscrypt: remove CRYPTO_CTR dependency	2019-01-23 23:56:43 -05:00
keyinfo.c	fscrypt: add Adiantum support	2019-01-06 08:36:21 -05:00
Makefile	fscrypt: new helper function - fscrypt_file_open()	2017-10-18 19:52:37 -04:00
policy.c	fscrypt: add Adiantum support	2019-01-06 08:36:21 -05:00