mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Eric Biggers" <ebiggers@kernel.org>, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	"Jason A . Donenfeld" <Jason@zx2c4.com>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	kunit-dev@googlegroups.com,
	"Brendan Higgins" <brendan.higgins@linux.dev>,
	"David Gow" <davidgow@google.com>,
	"Rae Moar" <raemoar63@gmail.com>
Subject: Re: [PATCH] lib/crypto: tests: Add a .kunitconfig file
Date: Mon, 02 Mar 2026 16:01:20 +0100	[thread overview]
Message-ID: <80de5b59-74d4-4009-9870-15bf2da35ce4@app.fastmail.com> (raw)
In-Reply-To: <20260301040140.490310-1-ebiggers@kernel.org>

On Sun, 1 Mar 2026, at 05:01, Eric Biggers wrote:
> Add a .kunitconfig file to the lib/crypto/ directory so that the crypto
> library tests can be run more easily using kunit.py.  Example with UML:
>
>     tools/testing/kunit/kunit.py run --kunitconfig=lib/crypto
>
> Example with QEMU:
>
>     tools/testing/kunit/kunit.py run --kunitconfig=lib/crypto 
> --arch=arm64 --make_options LLVM=1
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
>
> This is targeting libcrypto-fixes
>
>  lib/crypto/.kunitconfig | 34 ++++++++++++++++++++++++++++++++++
>  1 file changed, 34 insertions(+)
>  create mode 100644 lib/crypto/.kunitconfig
>

Acked-by: Ard Biesheuvel <ardb@kernel.org>

> diff --git a/lib/crypto/.kunitconfig b/lib/crypto/.kunitconfig
> new file mode 100644
> index 0000000000000..197d00065b4f5
> --- /dev/null
> +++ b/lib/crypto/.kunitconfig
> @@ -0,0 +1,34 @@
> +CONFIG_KUNIT=y
> +
> +# These kconfig options select all the CONFIG_CRYPTO_LIB_* symbols that have a
> +# corresponding KUnit test.  CONFIG_CRYPTO_LIB_* cannot be directly enabled
> +# here, since they are hidden symbols.
> +CONFIG_CRYPTO=y
> +CONFIG_CRYPTO_ADIANTUM=y
> +CONFIG_CRYPTO_BLAKE2B=y
> +CONFIG_CRYPTO_CHACHA20POLY1305=y
> +CONFIG_CRYPTO_HCTR2=y
> +CONFIG_CRYPTO_MD5=y
> +CONFIG_CRYPTO_MLDSA=y
> +CONFIG_CRYPTO_SHA1=y
> +CONFIG_CRYPTO_SHA256=y
> +CONFIG_CRYPTO_SHA512=y
> +CONFIG_CRYPTO_SHA3=y
> +CONFIG_INET=y
> +CONFIG_IPV6=y
> +CONFIG_NET=y
> +CONFIG_NETDEVICES=y
> +CONFIG_WIREGUARD=y
> +
> +CONFIG_CRYPTO_LIB_BLAKE2B_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_BLAKE2S_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_CURVE25519_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_MD5_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_MLDSA_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_NH_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_POLY1305_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_POLYVAL_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_SHA1_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_SHA256_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_SHA512_KUNIT_TEST=y
> +CONFIG_CRYPTO_LIB_SHA3_KUNIT_TEST=y
>
> base-commit: 4478e8eeb87120c11e90041864c2233238b2155a
> -- 
> 2.53.0

  reply	other threads:[~2026-03-02 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  4:01 Eric Biggers
2026-03-02 15:01 ` Ard Biesheuvel [this message]
2026-03-02 23:38 ` 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=80de5b59-74d4-4009-9870-15bf2da35ce4@app.fastmail.com \
    --to=ardb@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=brendan.higgins@linux.dev \
    --cc=davidgow@google.com \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raemoar63@gmail.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

all inboxes | Powered by JetHome®