[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250617201933.GF4037@suse.cz>
Date: Tue, 17 Jun 2025 22:19:33 +0200
From: David Sterba <dsterba@...e.cz>
To: Eric Biggers <ebiggers@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
Ard Biesheuvel <ardb@...nel.org>, linux-btrfs@...r.kernel.org,
Alexander Gordeev <agordeev@...ux.ibm.com>,
Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>,
David Sterba <dsterba@...e.com>
Subject: Re: [PATCH 0/2] Simplify the shash wrappers for the CRC32 library
On Fri, Jun 13, 2025 at 11:37:51AM -0700, Eric Biggers wrote:
> 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.
Yes, this is fine, I don't think any ABI applies here and the
implementation was only informative.
> 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
Acked-by: David Sterba <dsterba@...e.com>
Thanks.
Powered by blists - more mailing lists