From: Randy Dunlap <rdunlap@infradead.org>
To: "Kernel.org Bugbot" <bugbot@kernel.org>,
bugs@lists.linux.dev, linux-kselftest@vger.kernel.org,
skhan@linuxfoundation.org, shuah@kernel.org
Cc: linux-crypto@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: Kernel panic, CONFIG_FIPS_SIGNATURE_SELFTEST, missing dependency
Date: Tue, 4 Apr 2023 20:15:12 -0700 [thread overview]
Message-ID: <15521c65-1501-9394-8845-4d4ef983e6b6@infradead.org> (raw)
In-Reply-To: <20230404-b217293c6-010748a08594@bugzilla.kernel.org>
[adding linux-crypto and dhowells]
On 4/3/23 23:17, Kernel.org Bugbot wrote:
> o6irnndpcv7 writes via Kernel.org Bugzilla:
>
> Hi Randy!
>
> I submitted an example config.
> That config works fine for me, until I set:
>
> CONFIG_FIPS_SIGNATURE_SELFTEST=y
>
> And it starts working well again if I set:
>
> CONFIG_FIPS_SIGNATURE_SELFTEST=y
> CONFIG_CRYPTO_SHA256=y
>
> That's why I think it is related to FIPS_SIGNATURE_SELFTEST.
>
>
> Thanks,
> sephora
>
> View: https://bugzilla.kernel.org/show_bug.cgi?id=217293#c6
> You can reply to this message to join the discussion.
I'm not making any progress on this bug, so asking others for help.
Is there anything in the FIPS_SIGNATURE_SELFTEST code (selftest.c)
or code that it calls that requires CRYPTO_SHA256?
--
~Randy
prev parent reply other threads:[~2023-04-05 3:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 14:29 Kernel panic, CONFIG_FIPS_SIGNATURE_SELFTEST, missing dependency Kernel.org Bugbot
2023-04-03 16:33 ` Randy Dunlap
2023-04-03 20:04 ` Kernel.org Bugbot
2023-04-03 20:19 ` Randy Dunlap
2023-04-04 4:43 ` Randy Dunlap
2023-04-04 6:06 ` Kernel.org Bugbot
2023-04-04 6:17 ` Kernel.org Bugbot
2023-04-05 3:15 ` Randy Dunlap [this message]
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=15521c65-1501-9394-8845-4d4ef983e6b6@infradead.org \
--to=rdunlap@infradead.org \
--cc=bugbot@kernel.org \
--cc=bugs@lists.linux.dev \
--cc=dhowells@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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.