From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [GIT PULL] Crypto Fixes for 6.16
Date: Tue, 24 Jun 2025 20:04:04 -0700 [thread overview]
Message-ID: <20250625030404.GA8962@sol> (raw)
In-Reply-To: <aFtidDP6MLX1V2A6@gondor.apana.org.au>
On Wed, Jun 25, 2025 at 10:44:04AM +0800, Herbert Xu wrote:
> Hi Linus:
>
> The following changes since commit df29f60369ccec0aa17d7eed7e2ae1fcdc9be6d4:
>
> crypto: ahash - Fix infinite recursion in ahash_def_finup (2025-06-18 17:02:02 +0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git tags/v6.16-p6
>
> for you to fetch changes up to 20d71750cc72e80859d52548cf5c2a7513983b0d:
>
> crypto: wp512 - Use API partial block handling (2025-06-23 16:56:56 +0800)
>
> ----------------------------------------------------------------
> This push fixes a regression where wp512 can no longer be used
> with hmac.
> ----------------------------------------------------------------
>
> Herbert Xu (1):
> crypto: wp512 - Use API partial block handling
>
Wouldn't it make more sense to revert the "Crypto API partial block handling"
stuff? It's been causing a huge number of problems, and it's been getting
superseded by the librarification changes anyway.
This is already the fourth 6.16 fixes pull request for regressions caused by
your partial block handling changes. And I have another one queued in
libcrypto-fixes. I expect there will need to be more...
Indeed, I just found that a lot of drivers in drivers/crypto/ haven't been
updated to be aware of the extra byte that comes back from
crypto_shash_export(). So there are a bunch of buffer overflows there too.
(Not like drivers/crypto/ actually matters, but apparently your changes are for
its benefit? So it's interesting that it was actually broken by them.)
- Eric
next prev parent reply other threads:[~2025-06-25 3:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 2:44 [GIT PULL] Crypto Fixes for 6.16 Herbert Xu
2025-06-25 3:04 ` Eric Biggers [this message]
2025-06-25 3:14 ` Herbert Xu
2025-06-25 3:32 ` Eric Biggers
2025-06-25 3:49 ` Herbert Xu
2025-06-27 5:08 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-07-19 0:36 Herbert Xu
2025-07-19 1:34 ` pr-tracker-bot
2025-06-20 3:17 Herbert Xu
2025-06-20 6:34 ` pr-tracker-bot
2025-06-13 4:30 Herbert Xu
2025-06-13 18:04 ` pr-tracker-bot
2025-06-03 5:03 Herbert Xu
2025-06-03 16:09 ` pr-tracker-bot
2025-05-28 3:03 Herbert Xu
2025-05-28 22:16 ` pr-tracker-bot
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=20250625030404.GA8962@sol \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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