From: Eric Biggers <ebiggers3@gmail.com>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: David Howells <dhowells@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
Ulf Hansson <ulf.hansson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Mark Brown <broonie@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
John Stultz <john.stultz@linaro.org>,
Eric Biggers <ebiggers@google.com>,
crypto <linux-crypto@vger.kernel.org>,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: kernel failure while loading X.509 certificate
Date: Thu, 18 Jan 2018 10:12:05 -0800 [thread overview]
Message-ID: <20180118181205.4cwclwrh2x3zi5mz@gmail.com> (raw)
In-Reply-To: <CBA47A21-8E0C-4DFD-ACE5-3872AEAAEEC4@linaro.org>
On Thu, Jan 18, 2018 at 11:07:50AM +0100, Paolo Valente wrote:
>
>
> > Il giorno 17 gen 2018, alle ore 12:08, David Howells <dhowells@redhat.com> ha scritto:
> >
> > If this happened during boot, it could be that you have an X.509 cert for
> > which the digest algorithm isn't built into the kernel.
> >
>
> Yeah. I did look for such an inconsistency after that failure, but I
> didn't find it, most certainly because of my lack of expertise on
> this.
>
> After the success with rc8, I retried with rc7, repeating the same
> streamline_config.pl procedure as the first time. Of course, by
> Murphy's laws, rc7 worked this time. Sorry for making you waste
> your time. Should this happen again, I won't be so superficial not to
> make a backup of the offending config.
>
No your report is still useful; I think there is a real kernel bug here,
probably reproducible using add_key() with type "asymmetric", where the
signature's hash algorithm isn't supported by the kernel. I'll try to put
together a reproducer when I have a chance. Thanks!
Eric
prev parent reply other threads:[~2018-01-18 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F5505112-180F-4889-A73E-D0AB9054E58E@linaro.org>
2018-01-11 22:37 ` kernel failure while loading X.509 certificate Arnd Bergmann
2018-01-12 6:06 ` Paolo Valente
2018-01-17 5:16 ` Eric Biggers
2018-01-17 5:36 ` Paolo Valente
2018-01-17 5:44 ` Eric Biggers
2018-01-17 6:03 ` Paolo Valente
2018-01-17 11:08 ` David Howells
2018-01-18 10:07 ` Paolo Valente
2018-01-18 18:12 ` Eric Biggers [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=20180118181205.4cwclwrh2x3zi5mz@gmail.com \
--to=ebiggers3@gmail.com \
--cc=arnd@arndb.de \
--cc=broonie@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=dhowells@redhat.com \
--cc=ebiggers@google.com \
--cc=john.stultz@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=regressions@leemhuis.info \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.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