linux-kernel - Re: [PATCH 10/10] btrfs: switch to library APIs for checksums

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251023184537.GB20913@suse.cz>
Date: Thu, 23 Oct 2025 20:45:37 +0200
From: David Sterba <dsterba@...e.cz>
To: Eric Biggers <ebiggers@...nel.org>
Cc: linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-btrfs@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Ard Biesheuvel <ardb@...nel.org>,
	"Jason A . Donenfeld" <Jason@...c4.com>
Subject: Re: [PATCH 10/10] btrfs: switch to library APIs for checksums

On Wed, Oct 22, 2025 at 10:59:34AM -0700, Eric Biggers wrote:
> > Thanks, this simplifies quite a few things. I'd like to take it via the
> > btrfs tree as there may be the hash additions (XXH3, BLAKE3) but
> > currently I'm not sure if it won't make things more complicated. I
> > haven't started the kernel part yet so I can use this patchset for
> > development and rebase once it's merged. 
> 
> Great.  I'm planning to take patches 1-9 through libcrypto-next for
> 6.19.  You can then take patch 10 through the btrfs tree for 6.20.  Does
> that sound good?

Yes, the 6.20 schedule works better for me.

> We can work out the XXH3 and BLAKE3 support later.  If
> you'd like to add another checksum algorithm, I'd suggest picking just
> one.  btrfs already supports an awful lot of choices for the checksum.
> But we can discuss that later.

Yes, I'v deleted long answer to that, it would be better to discuss that
separately once the xxh3 and blake3 get posted.