linux/fs/crypto
Eric Biggers 6e1adb88d2 fscrypt: use crypto_skcipher_driver_name()
Crypto API users shouldn't really be accessing struct skcipher_alg
directly.  <crypto/skcipher.h> already has a function
crypto_skcipher_driver_name(), so use that instead.

No change in behavior.

Link: https://lore.kernel.org/r/20191209203810.225302-1-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
2019-12-31 10:33:50 -06:00
..
bio.c fscrypt: remove struct fscrypt_ctx 2019-10-21 13:22:08 -07:00
crypto.c fscrypt: add support for IV_INO_LBLK_64 policies 2019-11-06 12:34:36 -08:00
fname.c fscrypt: v2 encryption policy support 2019-08-12 19:18:50 -07:00
fscrypt_private.h fscrypt: add support for IV_INO_LBLK_64 policies 2019-11-06 12:34:36 -08:00
hkdf.c fscrypt: add an HKDF-SHA512 implementation 2019-08-12 19:18:50 -07:00
hooks.c fscrypt: make fscrypt_msg() take inode instead of super_block 2019-08-12 19:04:44 -07:00
Kconfig fscrypt: add an HKDF-SHA512 implementation 2019-08-12 19:18:50 -07:00
keyring.c fscrypt: support passing a keyring key to FS_IOC_ADD_ENCRYPTION_KEY 2019-12-31 10:33:49 -06:00
keysetup_v1.c fscrypt: invoke crypto API for ESSIV handling 2019-10-21 13:22:08 -07:00
keysetup.c fscrypt: use crypto_skcipher_driver_name() 2019-12-31 10:33:50 -06:00
Makefile fscrypt: add an HKDF-SHA512 implementation 2019-08-12 19:18:50 -07:00
policy.c fscrypt: add support for IV_INO_LBLK_64 policies 2019-11-06 12:34:36 -08:00