From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Thomas Huth <thuth@redhat.com>,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH 0/5] lib/crypto: KUnit tests for AES-CCM and AES-GCM
Date: Wed, 29 Jul 2026 18:32:55 -0700 [thread overview]
Message-ID: <20260730013301.160203-1-ebiggers@kernel.org> (raw)
This series applies to libcrypto-next. It can also be retrieved from:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git gcm-ccm-kunit-v1
This series adds comprehensive KUnit test suites for the AES-CCM and
AES-GCM library APIs.
This is a follow-up to the series
"[PATCH v2 00/13] Library APIs for AES encryption modes"
(https://lore.kernel.org/linux-crypto/20260715221153.246410-1-ebiggers@kernel.org/)
Eric Biggers (5):
lib/crypto: tests: Create test-utils.h
lib/crypto: tests: Use per-test-case buffers in hash tests
lib/crypto: tests: Add aead-test-template.h
lib/crypto: tests: Add KUnit test suite for AES-CCM
lib/crypto: tests: Add KUnit test suite for AES-GCM
lib/crypto/.kunitconfig | 2 +
lib/crypto/tests/Kconfig | 18 +
lib/crypto/tests/Makefile | 2 +
lib/crypto/tests/aead-test-template.h | 1039 +++++++++++++++++++++
lib/crypto/tests/aes_cbc_macs_kunit.c | 12 +-
lib/crypto/tests/aes_ccm_kunit.c | 352 +++++++
lib/crypto/tests/aes_gcm_kunit.c | 472 ++++++++++
lib/crypto/tests/blake2b_kunit.c | 33 +-
lib/crypto/tests/blake2s_kunit.c | 33 +-
lib/crypto/tests/chacha20poly1305_kunit.c | 9 +-
lib/crypto/tests/ghash_kunit.c | 37 +-
lib/crypto/tests/hash-test-template.h | 249 ++---
lib/crypto/tests/md5_kunit.c | 2 -
lib/crypto/tests/mldsa_kunit.c | 19 +-
lib/crypto/tests/nh_kunit.c | 5 +-
lib/crypto/tests/poly1305_kunit.c | 21 +-
lib/crypto/tests/polyval_kunit.c | 38 +-
lib/crypto/tests/sha1_kunit.c | 2 -
lib/crypto/tests/sha224_kunit.c | 2 -
lib/crypto/tests/sha256_kunit.c | 48 +-
lib/crypto/tests/sha384_kunit.c | 2 -
lib/crypto/tests/sha3_kunit.c | 30 +-
lib/crypto/tests/sha512_kunit.c | 2 -
lib/crypto/tests/sm3_kunit.c | 2 -
lib/crypto/tests/test-utils.h | 111 +++
scripts/crypto/gen-aead-testvecs.py | 69 ++
26 files changed, 2271 insertions(+), 340 deletions(-)
create mode 100644 lib/crypto/tests/aead-test-template.h
create mode 100644 lib/crypto/tests/aes_ccm_kunit.c
create mode 100644 lib/crypto/tests/aes_gcm_kunit.c
create mode 100644 lib/crypto/tests/test-utils.h
create mode 100755 scripts/crypto/gen-aead-testvecs.py
base-commit: f70ad727d1d60a4dfcb1a22152d4169f9a205af9
--
2.55.0
next reply other threads:[~2026-07-30 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 1:32 Eric Biggers [this message]
2026-07-30 1:32 ` [PATCH 1/5] lib/crypto: tests: Create test-utils.h Eric Biggers
2026-07-30 1:32 ` [PATCH 2/5] lib/crypto: tests: Use per-test-case buffers in hash tests Eric Biggers
2026-07-30 1:32 ` [PATCH 3/5] lib/crypto: tests: Add aead-test-template.h Eric Biggers
2026-07-30 1:32 ` [PATCH 4/5] lib/crypto: tests: Add KUnit test suite for AES-CCM Eric Biggers
2026-07-30 1:33 ` [PATCH 5/5] lib/crypto: tests: Add KUnit test suite for AES-GCM 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=20260730013301.160203-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thuth@redhat.com \
/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