From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
linux-btrfs@vger.kernel.org,
Alexander Gordeev <agordeev@linux.ibm.com>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Subject: [PATCH 0/2] Simplify the shash wrappers for the CRC32 library
Date: Fri, 13 Jun 2025 11:37:51 -0700 [thread overview]
Message-ID: <20250613183753.31864-1-ebiggers@kernel.org> (raw)
This series simplifies how the CRC32 library functions are exposed
through the crypto_shash API. We'll now have just one shash algorithm
each for "crc32" and "crc32c", and their driver names will just always
be "crc32-lib" and "crc32c-lib" respectively. This seems to be all
that's actually needed.
As mentioned in patch 2, this does change the content of
/sys/fs/btrfs/$uuid/checksum again, but that should be fine.
This is based on v6.16-rc1, and I'm planning to take these patches
through the crc-next tree. These supersede
https://lore.kernel.org/r/20250601224441.778374-2-ebiggers@kernel.org/
and
https://lore.kernel.org/r/20250601224441.778374-3-ebiggers@kernel.org/,
and they fix the warning in the full crypto self-tests reported at
https://lore.kernel.org/r/aExLZaoBCg55rZWJ@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com/
Eric Biggers (2):
btrfs: stop parsing crc32c driver name
crypto/crc32[c]: register only "-lib" drivers
crypto/Makefile | 2 --
crypto/crc32.c | 65 +++++----------------------------------------
crypto/crc32c.c | 66 ++++------------------------------------------
crypto/testmgr.c | 2 ++
fs/btrfs/disk-io.c | 8 ++----
5 files changed, 15 insertions(+), 128 deletions(-)
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
--
2.49.0
next reply other threads:[~2025-06-13 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 18:37 Eric Biggers [this message]
2025-06-13 18:37 ` [PATCH 1/2] btrfs: stop parsing crc32c driver name Eric Biggers
2025-06-13 18:37 ` [PATCH 2/2] crypto/crc32[c]: register only "-lib" drivers Eric Biggers
2025-06-17 20:17 ` David Sterba
2025-06-17 20:20 ` Eric Biggers
2025-06-17 20:47 ` Eric Biggers
2025-06-18 8:58 ` David Sterba
2025-06-19 10:27 ` Daniel Vacek
2025-06-19 12:59 ` David Sterba
2025-06-17 3:39 ` [PATCH 0/2] Simplify the shash wrappers for the CRC32 library Eric Biggers
2025-06-17 20:19 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250613183753.31864-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=ardb@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®