From: Mario Limonciello <mario.limonciello@amd.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Todd Brandt <todd.e.brandt@intel.com>,
Patrick Steinhardt <ps@pks.im>, Ronan Pigott <ronan@rjp.ie>,
Raymond Jay Golo <rjgolo@gmail.com>
Subject: Re: [PATCH v2] tpm: Don't make vendor check required for probe
Date: Tue, 22 Aug 2023 09:05:13 -0500 [thread overview]
Message-ID: <b7d45df7-3d1c-4b31-9da1-5f81d3e5b279@amd.com> (raw)
In-Reply-To: <CUZ3T3G99JG2.29X1G67HRO9QT@suppilovahvero>
On 8/22/2023 08:22, Jarkko Sakkinen wrote:
> On Mon Aug 21, 2023 at 5:02 PM EEST, Mario Limonciello wrote:
>> The vendor check introduced by commit 554b841d4703 ("tpm: Disable RNG for
>> all AMD fTPMs") doesn't work properly on a number of Intel fTPMs. On the
>> reported systems the TPM doesn't reply at bootup and returns back the
>> command code. This makes the TPM fail probe.
>>
>> As this isn't crucial for anything but AMD fTPM and AMD fTPM works, check
>> the chip vendor and if it's not AMD don't run the checks.
>>
>> Cc: stable@vger.kernel.org
>> Fixes: 554b841d4703 ("tpm: Disable RNG for all AMD fTPMs")
>> Reported-by: Todd Brandt <todd.e.brandt@intel.com>
>> Reported-by: Patrick Steinhardt <ps@pks.im>
>> Reported-by: Ronan Pigott <ronan@rjp.ie>
>> Reported-by: Raymond Jay Golo <rjgolo@gmail.com>
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217804
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>> ---
>> v1->v2:
>> * Check x86 vendor for AMD
>> ---
>> drivers/char/tpm/tpm_crb.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c
>> index 9eb1a18590123..7faf670201ccc 100644
>> --- a/drivers/char/tpm/tpm_crb.c
>> +++ b/drivers/char/tpm/tpm_crb.c
>> @@ -465,8 +465,12 @@ static bool crb_req_canceled(struct tpm_chip *chip, u8 status)
>>
>> static int crb_check_flags(struct tpm_chip *chip)
>> {
>> + int ret = 0;
>> +#ifdef CONFIG_X86
>> u32 val;
>> - int ret;
>> +
>> + if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD)
>> + return ret;
>>
>> ret = crb_request_locality(chip, 0);
>> if (ret)
>> @@ -481,6 +485,7 @@ static int crb_check_flags(struct tpm_chip *chip)
>>
>> release:
>> crb_relinquish_locality(chip, 0);
>> +#endif
>
> Looks much better but the main question here is that is this combination
> possible:
>
> 1. AMD CPU
> 2. Non-AMD fTPM (i.e. manufacturer property differs)
>
> BR, Jarkko
Yes that combination is possible.
Pluton TPM uses the tpm_crb driver.
next prev parent reply other threads:[~2023-08-22 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 14:02 [PATCH v2] tpm: Don't make vendor check required for probe Mario Limonciello
2023-08-22 3:33 ` Ronan Pigott
2023-08-22 11:50 ` Raymond Jay Golo
2023-08-22 13:22 ` Jarkko Sakkinen
2023-08-22 14:05 ` Mario Limonciello [this message]
2023-08-22 14:56 ` Jarkko Sakkinen
2023-08-22 19:50 ` Jerry Snitselaar
2023-08-22 20:29 ` Jarkko Sakkinen
2023-08-22 20:32 ` Jarkko Sakkinen
2023-08-22 20:39 ` Jarkko Sakkinen
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=b7d45df7-3d1c-4b31-9da1-5f81d3e5b279@amd.com \
--to=mario.limonciello@amd.com \
--cc=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ps@pks.im \
--cc=rjgolo@gmail.com \
--cc=ronan@rjp.ie \
--cc=stable@vger.kernel.org \
--cc=todd.e.brandt@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