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>,
	David Howells <dhowells@redhat.com>
Subject: [GIT PULL] Crypto library tests for 6.19
Date: Sat, 29 Nov 2025 18:44:01 -0800	[thread overview]
Message-ID: <20251130024401.GC12664@sol> (raw)

This is based on the "Crypto library updates for 6.19" pull request.

The following changes since commit 2dbb6f4a25d38fcf7d6c1c682e45a13e6bbe9562:

  fscrypt: Drop obsolete recommendation to enable optimized POLYVAL (2025-11-11 11:03:39 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git tags/libcrypto-tests-for-linus

for you to fetch changes up to 578fe3ff3d5bc9d851d597bb12dd74c22ad55ff8:

  crypto: testmgr - Remove polyval tests (2025-11-11 11:07:52 -0800)

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

- Add KUnit test suites for SHA-3, BLAKE2b, and POLYVAL. These are the
  algorithms that have new crypto library interfaces this cycle.

- Remove the crypto_shash POLYVAL tests. They're no longer needed
  because POLYVAL support was removed from crypto_shash. Better
  POLYVAL test coverage is now provided via the KUnit test suite.

----------------------------------------------------------------
David Howells (1):
      lib/crypto: tests: Add SHA3 kunit tests

Eric Biggers (4):
      lib/crypto: tests: Add KUnit tests for BLAKE2b
      lib/crypto: tests: Add additional SHAKE tests
      lib/crypto: tests: Add KUnit tests for POLYVAL
      crypto: testmgr - Remove polyval tests

 Documentation/crypto/sha3.rst       |  11 +
 crypto/tcrypt.c                     |   4 -
 crypto/testmgr.c                    |   6 -
 crypto/testmgr.h                    | 171 ---------------
 lib/crypto/tests/Kconfig            |  29 +++
 lib/crypto/tests/Makefile           |   3 +
 lib/crypto/tests/blake2b-testvecs.h | 342 +++++++++++++++++++++++++++++
 lib/crypto/tests/blake2b_kunit.c    | 133 ++++++++++++
 lib/crypto/tests/polyval-testvecs.h | 186 ++++++++++++++++
 lib/crypto/tests/polyval_kunit.c    | 223 +++++++++++++++++++
 lib/crypto/tests/sha3-testvecs.h    | 249 +++++++++++++++++++++
 lib/crypto/tests/sha3_kunit.c       | 422 ++++++++++++++++++++++++++++++++++++
 scripts/crypto/gen-hash-testvecs.py | 101 +++++++--
 13 files changed, 1682 insertions(+), 198 deletions(-)
 create mode 100644 lib/crypto/tests/blake2b-testvecs.h
 create mode 100644 lib/crypto/tests/blake2b_kunit.c
 create mode 100644 lib/crypto/tests/polyval-testvecs.h
 create mode 100644 lib/crypto/tests/polyval_kunit.c
 create mode 100644 lib/crypto/tests/sha3-testvecs.h
 create mode 100644 lib/crypto/tests/sha3_kunit.c

             reply	other threads:[~2025-11-30  2:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-30  2:44 Eric Biggers [this message]
2025-12-03  3:11 ` [GIT PULL] Crypto library tests for 6.19 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=20251130024401.GC12664@sol \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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 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.