From: Ard Biesheuvel <ardb@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
linux-crypto@vger.kernel.org, fsverity@lists.linux.dev,
dm-devel@lists.linux.dev, x86@kernel.org,
linux-arm-kernel@lists.infradead.org,
Sami Tolvanen <samitolvanen@google.com>,
Bart Van Assche <bvanassche@acm.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Mike Snitzer <snitzer@kernel.org>,
Jonathan Brassow <jbrassow@redhat.com>
Subject: Re: [PATCH v5 00/15] Optimize dm-verity and fsverity using multibuffer hashing
Date: Thu, 11 Jul 2024 08:10:32 +0200 [thread overview]
Message-ID: <CAMj1kXFsa83=1atXR4DksAgViw9j5dhc3fAautPpMoNYPzuRZw@mail.gmail.com> (raw)
In-Reply-To: <20240710181417.GA58377@google.com>
On Wed, 10 Jul 2024 at 20:14, Eric Biggers <ebiggers@kernel.org> wrote:
>
> On Wed, Jul 10, 2024 at 12:54:24PM +0200, Mikulas Patocka wrote:
> > Hi
> >
> > I'd like to ask what's the status of this patchset.
> >
> > Will Herbert accept it? What's the planned kernel version where it will
> > appear?
> >
> > Mikulas
>
> It's blocked by Herbert wanting to design the multibuffer hashing API in a more
> complex way that doesn't make sense. See the previous discussions. I don't
> know when Herbert will change his mind, so for now I've shifted my focus to the
> Android kernels.
Yeah, this is really quite unfortunate, especially since the
alternative approach doesn't appear to be forthcoming.
I'd prefer Eric's approach over what Herbert is proposing, as the
former is available today and only addressess problems that are
actually known to exist, rather than handwavy claims about what future
developments in IPsec or h/w crypto accelerators might make meaningful
use of.
prev parent reply other threads:[~2024-07-11 6:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 3:48 [PATCH v5 00/15] Optimize dm-verity and fsverity using multibuffer hashing Eric Biggers
2024-06-11 3:48 ` [PATCH v5 01/15] crypto: shash - add support for finup_mb Eric Biggers
2024-06-11 3:48 ` [PATCH v5 02/15] crypto: testmgr - generate power-of-2 lengths more often Eric Biggers
2024-06-11 3:48 ` [PATCH v5 03/15] crypto: testmgr - add tests for finup_mb Eric Biggers
2024-06-11 3:48 ` [PATCH v5 04/15] crypto: x86/sha256-ni - add support " Eric Biggers
2024-06-12 9:42 ` Herbert Xu
2024-06-12 15:27 ` Eric Biggers
2024-06-11 3:48 ` [PATCH v5 05/15] crypto: arm64/sha256-ce " Eric Biggers
2024-06-11 3:48 ` [PATCH v5 06/15] fsverity: improve performance by using multibuffer hashing Eric Biggers
2024-06-11 3:48 ` [PATCH v5 07/15] dm-verity: move hash algorithm setup into its own function Eric Biggers
2024-06-11 3:48 ` [PATCH v5 08/15] dm-verity: move data hash mismatch handling " Eric Biggers
2024-06-11 3:48 ` [PATCH v5 09/15] dm-verity: make real_digest and want_digest fixed-length Eric Biggers
2024-06-11 3:48 ` [PATCH v5 10/15] dm-verity: provide dma_alignment limit in io_hints Eric Biggers
2024-06-11 3:48 ` [PATCH v5 11/15] dm-verity: always "map" the data blocks Eric Biggers
2024-06-11 3:48 ` [PATCH v5 12/15] dm-verity: make verity_hash() take dm_verity_io instead of ahash_request Eric Biggers
2024-06-11 3:48 ` [PATCH v5 13/15] dm-verity: hash blocks with shash import+finup when possible Eric Biggers
2024-06-11 3:48 ` [PATCH v5 14/15] dm-verity: reduce scope of real and wanted digests Eric Biggers
2024-06-11 3:48 ` [PATCH v5 15/15] dm-verity: improve performance by using multibuffer hashing Eric Biggers
2024-06-12 9:31 ` Herbert Xu
2024-06-12 15:38 ` Eric Biggers
2024-06-12 19:14 ` Eric Biggers
2024-06-11 15:39 ` [PATCH v5 00/15] Optimize dm-verity and fsverity " Ard Biesheuvel
2024-06-11 16:27 ` Sami Tolvanen
2024-07-10 10:54 ` Mikulas Patocka
2024-07-10 18:14 ` Eric Biggers
2024-07-11 6:10 ` Ard Biesheuvel [this message]
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='CAMj1kXFsa83=1atXR4DksAgViw9j5dhc3fAautPpMoNYPzuRZw@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=bvanassche@acm.org \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=herbert@gondor.apana.org.au \
--cc=jbrassow@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=samitolvanen@google.com \
--cc=snitzer@kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).