[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210927085104.vq42feghtaqiv6ni@wrt>
Date: Mon, 27 Sep 2021 10:51:04 +0200
From: Andreas Rammhold <andreas@...mhold.de>
To: Ahmad Fatoum <a.fatoum@...gutronix.de>
Cc: Andreas Rammhold <andreas@...mhold.de>,
James Bottomley <jejb@...ux.ibm.com>,
Jarkko Sakkinen <jarkko@...nel.org>,
Mimi Zohar <zohar@...ux.ibm.com>,
David Howells <dhowells@...hat.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Sumit Garg <sumit.garg@...aro.org>,
linux-integrity@...r.kernel.org, keyrings@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] KEYS: trusted: Fix trusted key backends when building
as module
On 09:47 13.09.21, Ahmad Fatoum wrote:
> Dear trusted key maintainers,
>
> On 30.07.21 03:28, Andreas Rammhold wrote:
> > Before this commit the kernel could end up with no trusted key sources
> > even though both of the currently supported backends (TPM and TEE) were
> > compiled as modules. This manifested in the trusted key type not being
> > registered at all.
> >
> > When checking if a CONFIG_… preprocessor variable is defined we only
> > test for the builtin (=y) case and not the module (=m) case. By using
> > the IS_REACHABLE() macro we do test for both cases.
> >
> > Fixes: 5d0682be3189 ("KEYS: trusted: Add generic trusted keys framework")
> > Signed-off-by: Andreas Rammhold <andreas@...mhold.de>
> > Reviewed-by: Jarkko Sakkinen <jarkko@...nel.org>
> Does anyone intend to pick this up?
Did this end up in any tree by now? I am wondering if I should resend
the patch instead. Perhaps it was just overlooked?
Andi
Powered by blists - more mailing lists