diff options
| author | Eric Biggers <ebiggers@google.com> | 2019-12-09 23:38:10 +0300 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2019-12-31 19:33:50 +0300 |
| commit | 6e1adb88d230b08ad9a223ecaea1e6b238a9078f (patch) | |
| tree | 8ab0c4f06eec49a65109f7428647a96b1530783c /fs | |
| parent | 93edd392cad7485097c2e9068c764ae30083bb05 (diff) | |
| download | linux-6e1adb88d230b08ad9a223ecaea1e6b238a9078f.tar.xz | |
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>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/crypto/keysetup.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/fs/crypto/keysetup.c b/fs/crypto/keysetup.c index f577bb6613f9..c9f4fe955971 100644 --- a/fs/crypto/keysetup.c +++ b/fs/crypto/keysetup.c @@ -89,8 +89,7 @@ struct crypto_skcipher *fscrypt_allocate_skcipher(struct fscrypt_mode *mode, * first time a mode is used. */ pr_info("fscrypt: %s using implementation \"%s\"\n", - mode->friendly_name, - crypto_skcipher_alg(tfm)->base.cra_driver_name); + mode->friendly_name, crypto_skcipher_driver_name(tfm)); } crypto_skcipher_set_flags(tfm, CRYPTO_TFM_REQ_FORBID_WEAK_KEYS); err = crypto_skcipher_setkey(tfm, raw_key, mode->keysize); |