From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-arm-kernel@lists.infradead.org,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH v3 0/2] lib/crypto: arm64: Fix Poly1305 NEON resume carry loss
Date: Fri, 9 Oct 2026 14:53:52 +0200 [thread overview]
Message-ID: <20261009125354.315476-1-ebiggers@kernel.org> (raw)
This series fixes a lost carry bit in the arm64 Poly1305 implementation,
then adds a regression test for it.
Compared to v2 sent by Jérémy Jean, I cleaned up the verbose
LLM-generated text in the commit message of the fix commit, and I
replaced the LLM-generated minimal test case with a more comprehensive
one similar to the existing test cases in the file.
Note: the second commit has references to the commit ID of the first,
which I'll fix up when applying.
Eric Biggers (1):
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/tests/poly1305_kunit.c | 97 +++++++++++++++++++++++++++---
2 files changed, 89 insertions(+), 10 deletions(-)
base-commit: 572af6872e520c7102e58362ef7cd7c2ed4342be
--
2.56.0
next reply other threads:[~2026-10-09 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 12:53 Eric Biggers [this message]
2026-10-09 12:53 ` [PATCH v3 1/2] lib/crypto: arm64: Fix lost Poly1305 carry when resuming NEON state Eric Biggers
2026-10-09 16:13 ` Eric Biggers
2026-10-09 16:15 ` Jason A. Donenfeld
2026-10-09 12:53 ` [PATCH v3 2/2] lib/crypto: tests: Add Poly1305 split-update carry regression test Eric Biggers
2026-10-09 16:19 ` Jason A. Donenfeld
2026-10-09 17:25 ` [PATCH v3 0/2] lib/crypto: arm64: Fix Poly1305 NEON resume carry loss Eric Biggers
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=20261009125354.315476-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox