All of
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <>
To: Jarkko Sakkinen <>
	Mario Limonciello <>,
	Thorsten Leemhuis <>,
	James Bottomley <>
Subject: Re: [PATCH RFC] tpm: disable hwrng for known-defective AMD RNGs
Date: Fri, 10 Feb 2023 02:08:17 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Y+WVzAt/>

On Fri, Feb 10, 2023 at 02:54:36AM +0200, Jarkko Sakkinen wrote:
> On Thu, Feb 09, 2023 at 12:31:20PM -0300, Jason A. Donenfeld wrote:
> > Do not register a hwrng for certain AMD TPMs that are running an old
> What do you mean by "certain AMD TPMs"?
> > known-buggy revision. Do this by probing the TPM2_PT_MANUFACTURER,
> Which revision?
> > and failing when an "AMD"-manufactured TPM2 chip is below a threshold.
> What do you mean by "threshold"?
> This also lacks desription of:
> 1. What kind of changes are done.
> 2. Why do they they are reasonable.

YEP! And guess what? It doesn't matter at all one bit. Why? Because
Mario, the AMD engineer working on this, is tuned into the goal here and
he's the one who will be reworking this PoC draft into a real non-RFC
commit. We've been discussing this over on the bugzilla Thorsten sent to
you on Feb 2:

> > BROKEN BROKEN BROKEN - I just made the version numbers up and haven't
> > tested this because I don't actually have hardware for it. I'm posting
> > this so that Mario can take over its development and submit a v2 himself
> > once he has confirmed the versioning info from inside AMD.
> Is this paragraph meant for commit log?

Obviously not; did you read it?


      reply	other threads:[~2023-02-10  1:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 15:31 [PATCH RFC] tpm: disable hwrng for known-defective AMD RNGs Jason A. Donenfeld
2023-02-09 15:41 ` Limonciello, Mario
2023-02-09 17:26   ` Jason A. Donenfeld
2023-02-11 15:15   ` Linux regression tracking (Thorsten Leemhuis)
2023-02-10  0:54 ` Jarkko Sakkinen
2023-02-10  1:08   ` Jason A. Donenfeld [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.