Thread (41 messages) 41 messages, 6 authors, 2024-11-05

Re: [PATCH v2 04/18] crypto: crc32 - don't unnecessarily register arch algorithms

From: Ard Biesheuvel <ardb@kernel.org>
Date: 2024-11-02 09:59:14
Also in: linux-arch, linux-arm-kernel, linux-crypto, linux-ext4, linux-f2fs-devel, linux-mips, linux-riscv, linux-s390, linux-scsi, lkml, loongarch, sparclinux

On Sat, 2 Nov 2024 at 10:45, Herbert Xu [off-list ref] wrote:
Eric Biggers [off-list ref] wrote:
quoted
While testing this patchset I notice that none of the crypto API drivers for
crc32 or crc32c even need to be loaded on my system anymore, as everything on my
system that uses those algorithms (such as ext4) just uses the library APIs now.
That makes the "check /proc/crypto" trick stop working anyway.
What's stopping us from removing them altogether?
At least btrfs supports a variety of checksums/hashes (crc32c, xxhash,
sha) via the shash API.

There are some other remaining uses of crc32c using shash or sync
ahash where the algo is hardcoded (NVMe, infiniband) so I imagine
those might be candidates for conversion as well.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help