diff options
| author | Eric Biggers <ebiggers@kernel.org> | 2025-10-14 14:16:54 -0700 |
|---|---|---|
| committer | Mikulas Patocka <mpatocka@redhat.com> | 2025-10-20 15:47:17 +0200 |
| commit | 3ee6c4bc5307d9fcc681dc7ee15822a54b94b39c (patch) | |
| tree | d95bd646e1c67ab97a279fcbd9661078af680fb8 /scripts/gdb/linux/bpf.py | |
| parent | be4addb1914f00c60599495acacf4e24e9cb8237 (diff) | |
dm-verity: remove log message with shash driver name
I added this log message in commit bbf6a566920e ("dm verity: log the
hash algorithm implementation"), to help people debug issues where they
forgot to enable the architecture-optimized SHA-256 code in their
kconfig or accidentally enabled a slow hardware offload driver (such as
QCE) that overrode the faster CPU-accelerated code. However:
- The crypto layer now always enables the architecture-optimized SHA-1,
SHA-256, and SHA-512 code. Moreover, for simplicity the driver name
is now fixed at "sha1-lib", "sha256-lib", etc.
- dm-verity now uses crypto_shash instead of crypto_ahash, preventing
the mistake of accidentally using a slow driver such as QCE.
Therefore, this log message generally no longer provides useful
information. Remove it.
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Diffstat (limited to 'scripts/gdb/linux/bpf.py')
0 files changed, 0 insertions, 0 deletions