From: Jeremy Kerr <jk@codeconstruct.com.au>
To: "Mark Pearson" <markpearson@lenovo.com>,
"Thomas Weißschuh" <thomas@t-8ch.de>,
"Mickaël Salaün" <mic@digikod.net>
Cc: 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"
<linux-integrity@vger.kernel.org>
Subject: Re: [External] Re: [BUG] blacklist: Problem blacklisting hash (-13) during boot
Date: Mon, 27 Feb 2023 22:36:29 +0800 [thread overview]
Message-ID: <c5d674bd67735de460b19fd955f718bf8b604c1d.camel@codeconstruct.com.au> (raw)
In-Reply-To: <2a215e4d-bf55-b063-3f1f-a63f51cbdbfb@lenovo.com>
Hi Mark,
> I've been looking at this and the FW team are claiming that it's not
> caused by duplicate entries in the dbx table, which is honestly a bit
> confusing.
>
> We've been doing some more digging - but is there a possibility this
> is caused by something else?
I can't quite trace where the EACCES is coming from, I can't see any
obvious causes there - the blacklist key type doesn't have an ->update
operation, and the assoc_array insert doesn't look like it would fail.
However: if I delete one of the duplicate keys using the bios UI, then
the number of errors logged decreases by one.
Cheers,
Jeremy
next prev parent reply other threads:[~2023-02-27 14:36 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
2023-02-27 13:38 ` Mark Pearson
2023-02-27 14:36 ` Jeremy Kerr [this message]
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=c5d674bd67735de460b19fd955f718bf8b604c1d.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.