public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	Diederik de Haas <didi.debian@cknow.org>,
	Ingo Franzki <ifranzki@linux.ibm.com>
Subject: Re: [PATCH] crypto: testmgr - reinstate kconfig support for fast tests only
Date: Thu, 12 Jun 2025 17:03:35 +0800	[thread overview]
Message-ID: <aEqX53xTnGX2b9Gc@gondor.apana.org.au> (raw)
In-Reply-To: <20250612060931.GA200686@sol>

On Wed, Jun 11, 2025 at 11:09:31PM -0700, Eric Biggers wrote:
>
> It used to be:
> 
>     config CRYPTO_MANAGER_DISABLE_TESTS
>             bool "Disable run-time self tests"
>             default y
>             help
>               Disable run-time self tests that normally take place at
>               algorithm registration.
> 
> So the CONFIG_EXPERT dependency for the prompt would be new.  Are you sure?

When this was inverted I specifically asked for a dependency
on EXPERT so that normal users won't be bothered by a question
that had no relevance to them.

You then suggested a dependency on DEBUG_KERNEL which I accepted
because EXPERT happens to select that so they're practically
equivalent.

So make it depend on either DEBUG_KERNEL or EXPERT because normal
users should never see this question.  IOW we as developers should
select a sane default, whatever that may be.

> If you insist.  I hoped to get the people working on drivers to actually run the
> tests that they are supposed to.  The default y is appropriate for anyone
> actually doing development and/or testing, which is what the tests are supposed
> to be for.
> 
> But I guess that doesn't really happen, and distros are expected to run the
> reduced set of tests in production because upstream doesn't test the drivers.
> And they will want n here.

I share your concern.  One idea is to calculate a hash based on the
current time and print it out if and only if SELFTESTS_FULL is enabled.

Then we could require all driver submissions to include this message
as proof that they enabled this option.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2025-06-12  9:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 17:55 [PATCH] crypto: testmgr - reinstate kconfig support for fast tests only Eric Biggers
2025-06-11 18:53 ` Diederik de Haas
2025-06-11 19:04   ` Eric Biggers
2025-06-11 19:47     ` Diederik de Haas
2025-06-11 20:14       ` Eric Biggers
2025-06-12  5:55 ` Herbert Xu
2025-06-12  6:09   ` Eric Biggers
2025-06-12  9:03     ` Herbert Xu [this message]
2025-06-12 17:20       ` 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=aEqX53xTnGX2b9Gc@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=didi.debian@cknow.org \
    --cc=ebiggers@kernel.org \
    --cc=ifranzki@linux.ibm.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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