Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-s390@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Ingo Franzki <ifranzki@linux.ibm.com>
Subject: [GIT PULL] Crypto library fix for v6.16-rc6
Date: Tue, 8 Jul 2025 09:45:17 -0700	[thread overview]
Message-ID: <20250708164517.GA1255@sol> (raw)

The following changes since commit 64f7548aad63d2fbca2eeb6eb33361c218ebd5a5:

  lib/crypto: sha256: Mark sha256_choose_blocks as __always_inline (2025-06-20 13:22:03 -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 68279380266a5fa70e664de754503338e2ec3f43:

  crypto: s390/sha - Fix uninitialized variable in SHA-1 and SHA-2 (2025-07-03 10:27:26 -0700)

----------------------------------------------------------------

Fix an uninitialized variable in the s390 optimized SHA-1 and SHA-2.

Note that my librarification changes also fix this by greatly
simplifying how the s390 optimized SHA code is integrated.  However, we
need this separate fix for 6.16 and older versions.

----------------------------------------------------------------
Eric Biggers (1):
      crypto: s390/sha - Fix uninitialized variable in SHA-1 and SHA-2

 arch/s390/crypto/sha1_s390.c   | 2 ++
 arch/s390/crypto/sha512_s390.c | 3 +++
 2 files changed, 5 insertions(+)

             reply	other threads:[~2025-07-08 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 16:45 Eric Biggers [this message]
2025-07-08 20:40 ` [GIT PULL] Crypto library fix for v6.16-rc6 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=20250708164517.GA1255@sol \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=hca@linux.ibm.com \
    --cc=ifranzki@linux.ibm.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@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