From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Dusty Mabe" <dusty@dustymabe.com>,
"Mario Limonciello" <mario.limonciello@amd.com>
Cc: <linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
<charles.d.prestopine@intel.com>, <rafael.j.wysocki@intel.com>,
<len.brown@intel.com>, <stable@vger.kernel.org>,
"Todd Brandt" <todd.e.brandt@intel.com>
Subject: Re: [PATCH] tpm: Don't make vendor check required for probe
Date: Mon, 04 Sep 2023 21:15:04 +0300 [thread overview]
Message-ID: <CVAC6ASBH8W5.B7SB98LQT87B@suppilovahvero> (raw)
In-Reply-To: <7eaf0f76-5820-e404-905e-892610eaed36@dustymabe.com>
On Mon Aug 28, 2023 at 6:47 PM EEST, Dusty Mabe wrote:
>
>
> On 8/18/23 14:15, Mario Limonciello wrote:
> > The vendor check introduced by commit 554b841d4703 ("tpm: Disable RNG for
> > all AMD fTPMs") doesn't work properly on Intel fTPM. The TPM doesn't reply
> > at bootup and returns back the command code.
> >
> > As this isn't crucial for anything but AMD fTPM and AMD fTPM works, throw
> > away the error code to let Intel fTPM continue to work.
> >
>
> FWIW there is a Fedora bug where several people are reporting similar issues:
> https://bugzilla.redhat.com/show_bug.cgi?id=2232888
>
> Dusty
I just sent v4 with reported-by's added despite:
1. checkpatch.pl complaining about them
2. no mention of the bugzilla in the kernel documentation at least not
in the sections describing the process handling the patches
BR, Jarkko
prev parent reply other threads:[~2023-09-04 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 18:15 Mario Limonciello
2023-08-18 22:07 ` Jarkko Sakkinen
2023-08-18 22:38 ` Limonciello, Mario
2023-08-18 23:44 ` Jarkko Sakkinen
2023-08-18 23:57 ` Limonciello, Mario
2023-08-19 13:35 ` Patrick Steinhardt
2023-08-22 11:25 ` Jarkko Sakkinen
2023-08-28 15:47 ` Dusty Mabe
2023-09-04 18:15 ` Jarkko Sakkinen [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=CVAC6ASBH8W5.B7SB98LQT87B@suppilovahvero \
--to=jarkko@kernel.org \
--cc=charles.d.prestopine@intel.com \
--cc=dusty@dustymabe.com \
--cc=len.brown@intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael.j.wysocki@intel.com \
--cc=regressions@leemhuis.info \
--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
all inboxes | Powered by JetHome®