diff options
author | Eric Biggers <ebiggers@google.com> | 2018-12-05 20:54:13 -0800 |
---|---|---|
committer | Mike Snitzer <snitzer@redhat.com> | 2018-12-18 09:02:27 -0500 |
commit | bbf6a566920e1b0244b27b5f9882fb7f8bc83a31 (patch) | |
tree | a47c4fd6cac2e305d54d5b64a73fb38b342b0a13 /ipc | |
parent | af331ebae7e10699a023fcce4f0671a01419ee3c (diff) | |
download | linux-stable-bbf6a566920e1b0244b27b5f9882fb7f8bc83a31.tar.gz linux-stable-bbf6a566920e1b0244b27b5f9882fb7f8bc83a31.tar.bz2 linux-stable-bbf6a566920e1b0244b27b5f9882fb7f8bc83a31.zip |
dm verity: log the hash algorithm implementation
Log the hash algorithm's driver name when a dm-verity target is created.
This will help people determine whether the expected implementation is
being used. It can make an enormous difference; e.g., SHA-256 on ARM
can be 8x faster with the crypto extensions than without. It can also
be useful to know if an implementation using an external crypto
accelerator is being used instead of a software implementation.
Example message:
[ 35.281945] device-mapper: verity: sha256 using implementation "sha256-ce"
We've already found the similar message in fs/crypto/keyinfo.c to be
very useful.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions