From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Andreas Rammhold <andreas@rammhold.de>,
Mimi Zohar <zohar@linux.ibm.com>,
David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
James Bottomley <jejb@linux.ibm.com>
Cc: James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Sumit Garg <sumit.garg@linaro.org>,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] KEYS: trusted: Fix trusted key backends when building as module
Date: Mon, 11 Oct 2021 12:19:19 +0200 [thread overview]
Message-ID: <db5ea3c2-42df-420b-6813-f6ef2c30df6f@pengutronix.de> (raw)
In-Reply-To: <20211002214725.fqmtbfjwtlom745c@wrt>
Hello Mimi, David, Jarkko and James,
On 02.10.21 23:47, Andreas Rammhold wrote:
>> My mistake. Trusted and encrypted key types have always been defined
>> as tristate. Only when EVM selects encrypted keys, and by extension
>> trusted keys, are they builtin.
>
> So how do we go about this patch? Building the TPM support as module has
> broken actually using the trusted backend. This patch fixes that while
> still allowing it to be a builtin. If there is some configuration there
> a module isn't acceptable I am sure that is handled within Kconfig?
Can anyone of you four pick this up? Andreas' regression fix has
had Jarkko's Reviewed-by for close to two months and a half now.
Thanks,
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2021-10-11 10:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 1:28 [PATCH v3] KEYS: trusted: Fix trusted key backends when building as module Andreas Rammhold
2021-07-30 4:54 ` Sumit Garg
2021-07-30 6:14 ` Ahmad Fatoum
2021-09-13 7:47 ` Ahmad Fatoum
2021-09-27 8:51 ` Andreas Rammhold
2021-09-27 11:27 ` Mimi Zohar
2021-09-27 20:08 ` Andreas Rammhold
2021-09-27 20:33 ` Mimi Zohar
2021-09-27 20:55 ` Andreas Rammhold
2021-09-27 21:31 ` Mimi Zohar
2021-10-02 21:47 ` Andreas Rammhold
2021-10-11 10:19 ` Ahmad Fatoum [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=db5ea3c2-42df-420b-6813-f6ef2c30df6f@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=andreas@rammhold.de \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.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=serge@hallyn.com \
--cc=sumit.garg@linaro.org \
--cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).