From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
jgg@ziepe.ca, linux@dominikbrodowski.net,
linux-integrity@vger.kernel.org, daniil.stas@posteo.net,
peterhuewe@gmx.de
Subject: Re: [PATCH v3] tpm: Disable RNG for all AMD fTPMs
Date: Tue, 8 Aug 2023 00:28:01 +0200 [thread overview]
Message-ID: <ZNFv8f3r86zq3JSh@zx2c4.com> (raw)
In-Reply-To: <CUK5NKQKDAWO.2RCNF768IKZ9Q@wks-101042-mac.ad.tuni.fi>
On Sat, Aug 05, 2023 at 02:39:11AM +0300, Jarkko Sakkinen wrote:
> On Sat Aug 5, 2023 at 2:21 AM EEST, Mario Limonciello wrote:
> > On 8/4/23 17:54, Jarkko Sakkinen wrote:
> > > On Thu Aug 3, 2023 at 9:24 PM EEST, Mario Limonciello wrote:
> > >> The TPM RNG functionality is not necessary for entropy when the CPU
> > >> already supports the RDRAND instruction. The TPM RNG functionality
> > >> was previously disabled on a subset of AMD fTPM series, but reports
> > >> continue to show problems on some systems causing stutter root caused
> > >> to TPM RNG functionality.
> > >>
> > >> Expand disabling TPM RNG use for all AMD fTPMs whether they have versions
> > >> that claim to have fixed or not. To accomplish this, move the detection
> > >> into part of the TPM CRB registration and add a flag indicating that
> > >> the TPM should opt-out of registration to hwrng.
> > >>
> > >> Cc: stable@vger.kernel.org # 5.5+
> > >> Fixes: b006c439d58d ("hwrng: core - start hwrng kthread also for untrusted sources")
> > >> Fixes: f1324bbc4011 ("tpm: disable hwrng for fTPM on some AMD designs")
> > >> Fixes: 3ef193822b25 ("tpm_crb: fix fTPM on AMD Zen+ CPUs")
> > >> Reported-by: daniil.stas@posteo.net
> > >> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217719
> > >> Reported-by: bitlord0xff@gmail.com
> > >> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217212
> > >> Reviewed-by: Jason A. Donenfeld <Jason@zx2c4.com>
> > >> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> > >
> > > I will skip rc5 and send this for rc6 on Monday.
> > >
> > > Has anyone with suitable AMD system tested this?
> >
> > Probably obvious; but I tested with a system that can support both dTPM
> > and fTPM and swapped between the two before I sent it.
>
> Ok, great. I've tested that with non-AMD system things continue to
> work so I guess that is sufficient enough for:
>
> Tested-by: Jarkko Sakkinen <jarkko@kernel.org>
>
> BR, Jarkko
Why is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=554b841d470338a3b1d6335b14ee1cd0c8f5d754
in Linus' tree? After we told you on several email threads to take the
v3, and you said you would, you still took the v2? What are you doing?
I'm frustrated because this is not the first time you've been out
to lunch about this stuff. Now there's the wrong stable metadata and the
fix is incomplete. Shame.
next prev parent reply other threads:[~2023-08-07 22:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 18:24 [PATCH v3] tpm: Disable RNG for all AMD fTPMs Mario Limonciello
2023-08-04 13:28 ` Jason A. Donenfeld
2023-08-04 23:06 ` Jarkko Sakkinen
2023-08-04 22:54 ` Jarkko Sakkinen
2023-08-04 23:21 ` Mario Limonciello
2023-08-04 23:39 ` Jarkko Sakkinen
2023-08-07 22:28 ` Jason A. Donenfeld [this message]
2023-08-08 0:15 ` Mario Limonciello
2023-08-08 0:39 ` Jason A. Donenfeld
2023-08-08 3:26 ` Linus Torvalds
2023-08-08 17:19 ` Jason A. Donenfeld
2023-08-09 17:06 ` Linus Torvalds
2023-08-09 21:35 ` Jason A. Donenfeld
2023-08-10 15:37 ` Jarkko Sakkinen
2023-08-10 15:06 ` Jarkko Sakkinen
2023-08-10 15:14 ` Jason A. Donenfeld
2023-08-10 15:04 ` Jarkko Sakkinen
2023-08-10 14:42 ` Jarkko Sakkinen
2023-08-10 14:45 ` Limonciello, Mario
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=ZNFv8f3r86zq3JSh@zx2c4.com \
--to=jason@zx2c4.com \
--cc=daniil.stas@posteo.net \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mario.limonciello@amd.com \
--cc=peterhuewe@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox