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>,
Kees Cook <kees@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Nathan Chancellor <nathan@kernel.org>
Subject: [GIT PULL] Crypto library fixes for v6.16-rc3
Date: Wed, 18 Jun 2025 12:49:58 -0700 [thread overview]
Message-ID: <20250618194958.GA1312@sol> (raw)
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git tags/libcrypto-for-linus
for you to fetch changes up to 9d4204a8106fe7dc80e3f2e440c8f2ba1ba47319:
lib/crypto/poly1305: Fix arm64's poly1305_blocks_arch() (2025-06-16 12:51:34 -0700)
----------------------------------------------------------------
- Fix a regression in the arm64 Poly1305 code
- Fix a couple compiler warnings
----------------------------------------------------------------
Eric Biggers (1):
lib/crypto/poly1305: Fix arm64's poly1305_blocks_arch()
Kees Cook (1):
lib/crypto: Annotate crypto strings with nonstring
Nathan Chancellor (1):
lib/crypto/curve25519-hacl64: Disable KASAN with clang-17 and older
arch/arm64/lib/crypto/poly1305-glue.c | 4 +--
lib/crypto/Makefile | 4 +++
lib/crypto/aescfb.c | 8 +++---
lib/crypto/aesgcm.c | 46 +++++++++++++++++------------------
4 files changed, 33 insertions(+), 29 deletions(-)
next reply other threads:[~2025-06-18 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 19:49 Eric Biggers [this message]
2025-06-18 21:32 ` [GIT PULL] Crypto library fixes for v6.16-rc3 pr-tracker-bot
2025-06-18 21:40 ` Kent Overstreet
2025-06-18 21:59 ` Eric Biggers
2025-06-18 22:05 ` Kent Overstreet
2025-07-07 21:24 ` 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=20250618194958.GA1312@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=kees@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@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;
as well as URLs for NNTP newsgroup(s).