Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Joachim Vandersmissen" <git@jvdsn.com>
Cc: <linux-crypto@vger.kernel.org>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"David Howells" <dhowells@redhat.com>,
	"Simo Sorce" <simo@redhat.com>,
	"Stephan Mueller" <smueller@chronox.de>
Subject: Re: [PATCH v4 1/2] certs: Move RSA self-test data to separate file
Date: Mon, 13 May 2024 04:32:20 +0300	[thread overview]
Message-ID: <D184NU1V1GK5.38B7O2NKVESUE@kernel.org> (raw)
In-Reply-To: <70b6dbf0-eb54-4e23-a295-6f7f0d02a23c@jvdsn.com>

On Mon May 13, 2024 at 4:11 AM EEST, Joachim Vandersmissen wrote:
> On 5/12/24 6:11 PM, Jarkko Sakkinen wrote:
> > On Sat May 11, 2024 at 9:23 AM EEST, Joachim Vandersmissen wrote:
> >> v4: FIPS_SIGNATURE_SELFTEST_RSA is no longer user-configurable and will
> >> be set when the dependencies are fulfilled.
> >>
> >> ---8<---
> > This is in wrong place. If the patch is applied it will be included to
> > the kernel git log. Please put your log before diffstat.
> I will keep it in mind for the next round.
> >
> >> In preparation of adding new ECDSA self-tests, the existing data is
> >> moved to a separate file. A new configuration option is added to
> >> control the compilation of the separate file. This configuration option
> >> also enforces dependencies that were missing from the existing
> >> CONFIG_FIPS_SIGNATURE_SELFTEST option.
> > 1. Please just call the thing by its name instead of building tension
> >     with "the new configuration option".
> > 2. Lacks the motivation of adding a new configuration option.
> The configuration option is there to ensure that the RSA (or ECDSA) 
> self-tests only get compiled in when RSA (or ECDSA) is actually enabled. 
> Otherwise, the self-test will panic on boot. I can make this more 
> explicit in the commit message.
> >
> >> The old fips_signature_selftest is no longer an init function, but now
> >> a helper function called from fips_signature_selftest_rsa.
> > This is confusing, please remove.
> Fair enough, I'll remove it from the commit message.

Yeah, I mean it is good to enough to have a code change no need to
document it here :-)

> >
> > So why just send this and not this plus the selftest? Feels incomplete
> > to me.
>
> Do you mean the ECDSA self-test? I didn't include that one here because 
> I didn't want to make the commit too big.

So, I'd suggest to make a patch set with the second patch containing
the tests.

BR, Jarkko

  reply	other threads:[~2024-05-13  1:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11  6:23 [PATCH v4 1/2] certs: Move RSA self-test data to separate file Joachim Vandersmissen
2024-05-11  6:23 ` [PATCH v4 2/2] certs: Add ECDSA signature verification self-test Joachim Vandersmissen
2024-05-12  7:16   ` Herbert Xu
2024-05-12  7:16 ` [PATCH v4 1/2] certs: Move RSA self-test data to separate file Herbert Xu
2024-05-12 23:11 ` Jarkko Sakkinen
2024-05-13  1:11   ` Joachim Vandersmissen
2024-05-13  1:32     ` Jarkko Sakkinen [this message]
2024-05-13  1:43       ` Joachim Vandersmissen
2024-05-13  3:27         ` Jarkko Sakkinen
2024-05-13  3:32           ` Jarkko Sakkinen

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=D184NU1V1GK5.38B7O2NKVESUE@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=git@jvdsn.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=simo@redhat.com \
    --cc=smueller@chronox.de \
    /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