All of lore.kernel.org
 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,
	Ard Biesheuvel <ardb@kernel.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Diederik de Haas <diederik@cknow-tech.com>,
	Jerry Shih <jerry.shih@sifive.com>,
	Vivian Wang <wangruikang@iscas.ac.cn>
Subject: [GIT PULL] Crypto library fixes for v6.19-rc1
Date: Thu, 11 Dec 2025 19:58:18 -0800	[thread overview]
Message-ID: <20251212035818.GA4838@sol> (raw)

The following changes since commit 7a3984bbd69055898add0fe22445f99435f33450:

  Merge tag 'mips_6.19' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux (2025-12-10 06:20:22 +0900)

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 f6a458746f905adb7d70e50e8b9383dc9e3fd75f:

  crypto: arm64/ghash - Fix incorrect output from ghash-neon (2025-12-10 09:46:26 -0800)

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

Fixes for some recent regressions as well as some longstanding issues:

 - Fix incorrect output from the arm64 NEON implementation of GHASH

 - Merge the ksimd scopes in the arm64 XTS code to reduce stack usage

 - Roll up the BLAKE2b round loop on 32-bit kernels to greatly reduce
   code size and stack usage

 - Add missing RISCV_EFFICIENT_VECTOR_UNALIGNED_ACCESS dependency

 - Fix chacha-riscv64-zvkb.S to not use frame pointer for data

----------------------------------------------------------------
Ard Biesheuvel (2):
      crypto/arm64: aes/xts - Use single ksimd scope to reduce stack bloat
      crypto/arm64: sm4/xts - Merge ksimd scopes to reduce stack bloat

Eric Biggers (4):
      lib/crypto: riscv: Depend on RISCV_EFFICIENT_VECTOR_UNALIGNED_ACCESS
      lib/crypto: blake2b: Roll up BLAKE2b round loop on 32-bit
      lib/crypto: blake2s: Replace manual unrolling with unrolled_full
      crypto: arm64/ghash - Fix incorrect output from ghash-neon

Vivian Wang (1):
      lib/crypto: riscv/chacha: Avoid s0/fp register

 arch/arm64/crypto/aes-glue.c           | 75 ++++++++++++++++------------------
 arch/arm64/crypto/aes-neonbs-glue.c    | 44 ++++++++++----------
 arch/arm64/crypto/ghash-ce-glue.c      |  2 +-
 arch/arm64/crypto/sm4-ce-glue.c        | 42 +++++++++----------
 arch/riscv/crypto/Kconfig              | 12 ++++--
 lib/crypto/Kconfig                     |  9 ++--
 lib/crypto/Makefile                    |  1 -
 lib/crypto/blake2b.c                   | 44 +++++++++-----------
 lib/crypto/blake2s.c                   | 38 ++++++++---------
 lib/crypto/riscv/chacha-riscv64-zvkb.S |  5 +--
 10 files changed, 130 insertions(+), 142 deletions(-)

             reply	other threads:[~2025-12-12  3:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12  3:58 Eric Biggers [this message]
2025-12-12 10:08 ` [GIT PULL] Crypto library fixes for v6.19-rc1 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=20251212035818.GA4838@sol \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=diederik@cknow-tech.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jerry.shih@sifive.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wangruikang@iscas.ac.cn \
    /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.