From: Johannes Berg <johannes@sipsolutions.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
"Wu, Fengguang" <fengguang.wu@intel.com>,
David Howells <dhowells@redhat.com>,
Kees Cook <keescook@chromium.org>,
Josh Boyer <jwboyer@redhat.com>
Cc: "Ye, Xiaolong" <xiaolong.ye@intel.com>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: d7be102f29 ("cfg80211: initialize regulatory keys/database later"): kernel BUG at crypto/asymmetric_keys/public_key.c:80!
Date: Mon, 27 Nov 2017 22:52:21 +0100 [thread overview]
Message-ID: <1511819541.5456.19.camel@sipsolutions.net> (raw)
In-Reply-To: <CA+55aFzviYrQa8Tn-R96nAL8YRv9t-wQfqOWNW05g6_WCWfgAA@mail.gmail.com>
On Mon, 2017-11-27 at 21:46 +0000, Linus Torvalds wrote:
> On Sat, Nov 25, 2017 at 7:07 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > FYI, we noticed the following commit (built with gcc-4.8):
> >
> > commit: d7be102f2945a626f55e0501e52bb31ba3e77b81 ("cfg80211: initialize regulatory keys/database later")
>
> The attached 'dmesg.xz' doesn't actually match the kernel or the
> report. Very odd.
>
> > [ 8.602885] kernel BUG at crypto/asymmetric_keys/public_key.c:80!
>
> In that reported kernel, that is
>
> 80 BUG_ON(!sig->digest);
>
> so the public key signature has no digest.
Yeah. I believe this was fixed by commit 01a95b2141e3 ("cfg80211:
select CRYPTO_SHA256 if needed"), and since that was already on the way
I didn't reply to this report specifically.
> I'm not seeing why it would ever be ok to do BUG_ON() instead of just
> returning an error, though.
That's kinda a good question - here we might fail to load this
certificate, print a key, and then never be able to load the signed
file - but at least we wouldn't crash immediately :-)
johannes
next prev parent reply other threads:[~2017-11-27 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 3:07 Fengguang Wu
2017-11-27 21:46 ` Linus Torvalds
2017-11-27 21:52 ` Johannes Berg [this message]
2017-11-27 23:25 ` David Howells
2017-11-27 23:30 ` Kees Cook
2017-11-27 23:31 ` Linus Torvalds
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=1511819541.5456.19.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dhowells@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=jwboyer@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=torvalds@linux-foundation.org \
--cc=xiaolong.ye@intel.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®