diff options
| author | Eric Biggers <ebiggers@google.com> | 2022-04-13 22:34:15 -0700 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2022-04-13 22:35:25 -0700 |
| commit | a7a5bc5fe8acc9381e38a34ef18f1115c5c22079 (patch) | |
| tree | 1c5079e222ecf12e15f3370671fa59ccb7272dfc /fs/crypto/keysetup.c | |
| parent | 63cec1389e116ae0e2a15e612a5b49651e04be3f (diff) | |
| download | linux-stable-a7a5bc5fe8acc9381e38a34ef18f1115c5c22079.tar.gz linux-stable-a7a5bc5fe8acc9381e38a34ef18f1115c5c22079.tar.bz2 linux-stable-a7a5bc5fe8acc9381e38a34ef18f1115c5c22079.zip | |
fscrypt: log when starting to use inline encryption
When inline encryption is used, the usual message "fscrypt: AES-256-XTS
using implementation <impl>" doesn't appear in the kernel log. Add a
similar message for the blk-crypto case that indicates that inline
encryption was used, and whether blk-crypto-fallback was used or not.
This can be useful for debugging performance problems.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Link: https://lore.kernel.org/r/20220414053415.158986-1-ebiggers@kernel.org
Diffstat (limited to 'fs/crypto/keysetup.c')
| -rw-r--r-- | fs/crypto/keysetup.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/crypto/keysetup.c b/fs/crypto/keysetup.c index eede186b04ce..6b509af13e0d 100644 --- a/fs/crypto/keysetup.c +++ b/fs/crypto/keysetup.c @@ -94,7 +94,7 @@ fscrypt_allocate_skcipher(struct fscrypt_mode *mode, const u8 *raw_key, mode->cipher_str, PTR_ERR(tfm)); return tfm; } - if (!xchg(&mode->logged_impl_name, 1)) { + if (!xchg(&mode->logged_cryptoapi_impl, 1)) { /* * fscrypt performance can vary greatly depending on which * crypto algorithm implementation is used. Help people debug |