diff options
| author | Eric Biggers <ebiggers@google.com> | 2022-04-14 08:34:15 +0300 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2022-04-14 08:35:25 +0300 |
| commit | a7a5bc5fe8acc9381e38a34ef18f1115c5c22079 (patch) | |
| tree | 1c5079e222ecf12e15f3370671fa59ccb7272dfc /fs/crypto/fscrypt_private.h | |
| parent | 63cec1389e116ae0e2a15e612a5b49651e04be3f (diff) | |
| download | linux-a7a5bc5fe8acc9381e38a34ef18f1115c5c22079.tar.xz | |
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/fscrypt_private.h')
| -rw-r--r-- | fs/crypto/fscrypt_private.h | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/fs/crypto/fscrypt_private.h b/fs/crypto/fscrypt_private.h index 5b0a9e6478b5..33f08f1b1974 100644 --- a/fs/crypto/fscrypt_private.h +++ b/fs/crypto/fscrypt_private.h @@ -561,7 +561,9 @@ struct fscrypt_mode { int keysize; /* key size in bytes */ int security_strength; /* security strength in bytes */ int ivsize; /* IV size in bytes */ - int logged_impl_name; + int logged_cryptoapi_impl; + int logged_blk_crypto_native; + int logged_blk_crypto_fallback; enum blk_crypto_mode_num blk_crypto_mode; }; |