From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ard Biesheuvel" <ardb@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Jérémy Jean" <Jeremy.Jean@oss.cyber.gouv.fr>,
Sashiko <sashiko-bot@kernel.org>
Subject: [GIT PULL] Crypto library fixes for 7.3-final
Date: Wed, 14 Oct 2026 15:15:20 +0200 [thread overview]
Message-ID: <20261014131520.GA97513@quark> (raw)
The following changes since commit 572af6872e520c7102e58362ef7cd7c2ed4342be:
crypto: aes - Fix undesired override of some optimized AES modes (2026-09-30 08:38:06 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git tags/libcrypto-fixes-for-linus
for you to fetch changes up to 7b817748bf083ad715a8d70de63f2184178cc372:
lib/crypto: tests: Add Poly1305 split-update carry regression test (2026-10-09 19:21:07 +0200)
----------------------------------------------------------------
Fix two Poly1305 bugs including a lost carry bit, and add a regression
test.
----------------------------------------------------------------
Eric Biggers (2):
lib/crypto: poly1305: Use memzero_explicit() in poly1305_final()
lib/crypto: tests: Add Poly1305 split-update carry regression test
Jérémy Jean (1):
lib/crypto: arm64: Fix lost Poly1305 carry when resuming NEON state
lib/crypto/arm64/poly1305-armv8.pl | 2 +-
lib/crypto/poly1305.c | 2 +-
lib/crypto/tests/poly1305_kunit.c | 97 ++++++++++++++++++++++++++++++++++----
3 files changed, 90 insertions(+), 11 deletions(-)
next reply other threads:[~2026-10-14 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 13:15 Eric Biggers [this message]
2026-10-14 15:28 ` [GIT PULL] Crypto library fixes for 7.3-final 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=20261014131520.GA97513@quark \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=Jeremy.Jean@oss.cyber.gouv.fr \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashiko-bot@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 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.