From: Jeremy Kerr <jk@codeconstruct.com.au>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: "Mark Pearson" <markpearson@lenovo.com>,
"Mickaël Salaün" <mic@digikod.net>,
"Jarkko Sakkinen" <jarkko@kernel.org>,
"David Howells" <dhowells@redhat.com>,
"David Woodhouse" <dwmw2@infradead.org>,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
linux-integrity@vger.kernel.org
Subject: Re: [External] Re: [BUG] blacklist: Problem blacklisting hash (-13) during boot
Date: Mon, 27 Feb 2023 09:42:39 +0800 [thread overview]
Message-ID: <e8190083513e08b2d237ee428ee6606de2c29b91.camel@codeconstruct.com.au> (raw)
In-Reply-To: <860048ca-d827-4319-9755-9b44ba3c4157@t-8ch.de>
Hi Thomas,
> > Given there's (at least) a few months' worth of GA machines with
> > this issue, can we suppress the warning?
>
> In 6.3 this message will be downgraded to a warning.
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c95e8f6fd157b45ef0685c221931561e943e82da
Nice, thanks for that.
> A fixed firmware is still desirable, though.
Yep, definitely.
Not to discourage a firmware fix, but I could look at adding support to
one of the utils (mokutil?) to delete duplicate kek/db/dbx entries...
Cheers,
Jeremy
next prev parent reply other threads:[~2023-02-27 1:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 3:16 [BUG] blacklist: Problem blacklisting hash (-13) during boot Thomas Weißschuh
2022-11-04 17:03 ` Mickaël Salaün
2022-11-04 19:11 ` Thomas Weißschuh
2022-11-04 20:12 ` [External] " Mark Pearson
2023-02-26 3:42 ` Jeremy Kerr
2023-02-26 4:28 ` Thomas Weißschuh
2023-02-27 1:42 ` Jeremy Kerr [this message]
2023-02-27 13:38 ` Mark Pearson
2023-02-27 14:36 ` Jeremy Kerr
2023-03-07 13:45 ` Mark Pearson
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=e8190083513e08b2d237ee428ee6606de2c29b91.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=markpearson@lenovo.com \
--cc=mic@digikod.net \
--cc=thomas@t-8ch.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 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.