From: Herbert Xu <herbert@gondor.apana.org.au>
To: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: [PATCH 00/12] crypto: sha256 - Use partial block API
Date: Wed, 30 Apr 2025 14:06:15 +0800 [thread overview]
Message-ID: <cover.1745992998.git.herbert@gondor.apana.org.au> (raw)
This is based on
https://patchwork.kernel.org/project/linux-crypto/list/?series=957785
Rather than going through the lib/sha256 partial block handling,
use the native shash partial block API. Add two extra shash
algorithms to provide testing coverage for lib/sha256.
Herbert Xu (12):
crypto: lib/sha256 - Restore lib_sha256 finup code
crypto: sha256 - Use the partial block API for generic
crypto: arm/sha256 - Add simd block function
crypto: arm64/sha256 - Add simd block function
crypto: mips/sha256 - Export block functions as GPL only
crypto: powerpc/sha256 - Export block functions as GPL only
crypto: riscv/sha256 - Add simd block function
crypto: s390/sha256 - Export block functions as GPL only
crypto: sparc/sha256 - Export block functions as GPL only
crypto: x86/sha256 - Add simd block function
crypto: lib/sha256 - Use generic block helper
crypto: sha256 - Use the partial block API
arch/arm/lib/crypto/Kconfig | 1 +
arch/arm/lib/crypto/sha256-armv4.pl | 20 +--
arch/arm/lib/crypto/sha256.c | 16 +--
arch/arm64/crypto/sha512-glue.c | 6 +-
arch/arm64/lib/crypto/Kconfig | 1 +
arch/arm64/lib/crypto/sha2-armv8.pl | 2 +-
arch/arm64/lib/crypto/sha256.c | 16 +--
.../mips/cavium-octeon/crypto/octeon-sha256.c | 4 +-
arch/powerpc/lib/crypto/sha256.c | 4 +-
arch/riscv/lib/crypto/Kconfig | 1 +
arch/riscv/lib/crypto/sha256.c | 17 ++-
arch/s390/lib/crypto/sha256.c | 4 +-
arch/sparc/lib/crypto/sha256.c | 4 +-
arch/x86/lib/crypto/Kconfig | 1 +
arch/x86/lib/crypto/sha256.c | 16 ++-
crypto/sha256.c | 134 +++++++++++-------
include/crypto/internal/sha2.h | 46 ++++++
include/crypto/sha2.h | 14 +-
lib/crypto/Kconfig | 8 ++
lib/crypto/sha256.c | 100 +++----------
20 files changed, 232 insertions(+), 183 deletions(-)
--
2.39.5
next reply other threads:[~2025-04-30 6:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 6:06 Herbert Xu [this message]
2025-04-30 6:06 ` [PATCH 01/12] crypto: lib/sha256 - Restore lib_sha256 finup code Herbert Xu
2025-04-30 6:06 ` [PATCH 02/12] crypto: sha256 - Use the partial block API for generic Herbert Xu
2025-04-30 6:06 ` [PATCH 03/12] crypto: arm/sha256 - Add simd block function Herbert Xu
2025-04-30 6:06 ` [PATCH 04/12] crypto: arm64/sha256 " Herbert Xu
2025-04-30 6:06 ` [PATCH 05/12] crypto: mips/sha256 - Export block functions as GPL only Herbert Xu
2025-04-30 6:06 ` [PATCH 06/12] crypto: powerpc/sha256 " Herbert Xu
2025-04-30 6:06 ` [PATCH 07/12] crypto: riscv/sha256 - Add simd block function Herbert Xu
2025-04-30 6:06 ` [PATCH 08/12] crypto: s390/sha256 - Export block functions as GPL only Herbert Xu
2025-04-30 6:06 ` [PATCH 09/12] crypto: sparc/sha256 " Herbert Xu
2025-04-30 6:06 ` [PATCH 10/12] crypto: x86/sha256 - Add simd block function Herbert Xu
2025-04-30 6:06 ` [PATCH 11/12] crypto: lib/sha256 - Use generic block helper Herbert Xu
2025-04-30 6:06 ` [PATCH 12/12] crypto: sha256 - Use the partial block API Herbert Xu
2025-04-30 17:45 ` [PATCH 00/12] crypto: sha256 - Use " Eric Biggers
2025-05-01 1:21 ` Herbert Xu
2025-05-01 2:26 ` Eric Biggers
2025-05-01 5:19 ` Herbert Xu
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=cover.1745992998.git.herbert@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--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