From: Eric Biggers <ebiggers@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org,
"Jason A . Donenfeld" <Jason@zx2c4.com>
Subject: Re: [PATCH] bcachefs: use library APIs for ChaCha20 and Poly1305
Date: Wed, 2 Apr 2025 09:28:47 -0700 [thread overview]
Message-ID: <20250402162847.GA1235@sol.localdomain> (raw)
In-Reply-To: <icwysnfc3v7b2hpwvm6ay6567sb5zcmcctmlt44cag6gblaylv@ubrzwcmphci2>
On Wed, Apr 02, 2025 at 10:01:07AM -0400, Kent Overstreet wrote:
> On Tue, Apr 01, 2025 at 09:33:33PM -0700, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > Just use the ChaCha20 and Poly1305 libraries instead of the clunky
> > crypto API. This is much simpler. It is also slightly faster, since
> > the libraries provide more direct access to the same
> > architecture-optimized ChaCha20 and Poly1305 code.
> >
> > I've tested that existing encrypted bcachefs filesystems can be continue
> > to be accessed with this patch applied.
> >
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
>
> Fantastic!
>
> Applied, and this should go into 6.15 - this should get the strange bugs
> in the poly1305 path that I wasn't able to reproduce off the dashboard
> (and if they're still there, they'll be much easier to debug.)
Thanks!
If you're referring to
https://lore.kernel.org/r/CAHOo4gLWAbArwg+w+AqqkxGmOFX6cm8Tvy85tb4igN6V7Z9BZQ@mail.gmail.com/,
I think bcachefs passed invalid memory to Poly1305 as a result of mounting a
fuzzed filesystem image. So it should be unaffected by this patch.
- Eric
next prev parent reply other threads:[~2025-04-02 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 4:33 [PATCH] bcachefs: use library APIs for ChaCha20 and Poly1305 Eric Biggers
2025-04-02 6:20 ` Ard Biesheuvel
2025-04-02 14:01 ` Kent Overstreet
2025-04-02 16:28 ` Eric Biggers [this message]
2025-04-02 16:33 ` Kent Overstreet
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=20250402162847.GA1235@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.