All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniil Stas <daniil.stas@posteo.net>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: James.Bottomley@hansenpartnership.com, Jason@zx2c4.com,
	jarkko@kernel.org, linux-integrity@vger.kernel.org,
	linux-kernel@vger.kernel.org, regressions@leemhuis.info,
	stable@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH 1/1] tpm: disable hwrng for fTPM on some AMD designs
Date: Thu, 27 Jul 2023 17:05:27 +0000	[thread overview]
Message-ID: <20230727200527.4080c595@g14> (raw)
In-Reply-To: <67eefe98-e6df-e152-3169-44329e22478d@amd.com>

On Thu, 27 Jul 2023 11:51:21 -0500
Mario Limonciello <mario.limonciello@amd.com> wrote:

> On 7/27/2023 11:50, Daniil Stas wrote:
> > On Thu, 27 Jul 2023 11:41:55 -0500
> > Mario Limonciello <mario.limonciello@amd.com> wrote:
> >   
> >> On 7/27/2023 11:39, Daniil Stas wrote:  
>  [...]  
>  [...]  
> >>   [...]  
>  [...]  
>  [...]  
> >>
> >> drivers/other is fine.  If there is a better category we can move
> >> it later.  
> > 
> > I see there are already several bug reports similar to mine. This
> > one for example: https://bugzilla.kernel.org/show_bug.cgi?id=217212
> > Should I still make a new one?  
> 
> Yes; please make a separate one.  If we decide it's the same we can 
> always mark as a duplicate.

Here is the bug report I created:
https://bugzilla.kernel.org/show_bug.cgi?id=217719

  reply	other threads:[~2023-07-27 17:05 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 20:19 [PATCH 0/1] Avoid triggering an fTPM bug from kernel Mario Limonciello
2023-02-14 20:19 ` [PATCH 1/1] tpm: disable hwrng for fTPM on some AMD designs Mario Limonciello
2023-02-17 15:18   ` Thorsten Leemhuis
2023-02-17 22:35     ` Jarkko Sakkinen
2023-02-18  2:25       ` Limonciello, Mario
2023-02-21 22:53         ` Jarkko Sakkinen
2023-02-21 23:10           ` Limonciello, Mario
2023-02-27 10:57             ` Thorsten Leemhuis
2023-02-27 11:14               ` Jarkko Sakkinen
2023-02-27 11:16                 ` Jarkko Sakkinen
2023-02-17 22:05   ` Jarkko Sakkinen
2023-07-27 15:38   ` Daniil Stas
2023-07-27 15:42     ` Mario Limonciello
2023-07-27 16:39       ` Daniil Stas
2023-07-27 16:41         ` Mario Limonciello
2023-07-27 16:50           ` Daniil Stas
2023-07-27 16:51             ` Mario Limonciello
2023-07-27 17:05               ` Daniil Stas [this message]
2023-07-28 20:41                 ` Linus Torvalds
2023-07-28 21:01                   ` Limonciello, Mario
2023-07-28 21:38                     ` Linus Torvalds
2023-07-28 21:47                       ` Limonciello, Mario
     [not found]                   ` <CUGAV1Y993FB.1O2Q691015Z2C@seitikki>
2023-07-31 19:05                     ` Linus Torvalds
2023-07-31 19:18                       ` Limonciello, Mario
2023-07-31 19:30                         ` Linus Torvalds
2023-07-31 21:57                           ` Limonciello, Mario
2023-07-31 23:28                             ` Linus Torvalds
2023-07-31 23:40                               ` Jason A. Donenfeld
2023-08-01  3:04                                 ` Mario Limonciello
2023-08-01 11:36                                   ` Mateusz Schyboll
2023-08-01 18:52                                   ` Jarkko Sakkinen
2023-08-01 18:55                                     ` Jarkko Sakkinen
2023-08-01 18:28                       ` Jarkko Sakkinen
2023-08-01 18:42                         ` Linus Torvalds
2023-08-01 18:51                           ` Mario Limonciello
2023-08-01 19:09                           ` Jarkko Sakkinen
2023-08-02 23:13                             ` Jerry Snitselaar
2023-08-03  0:34                               ` Stefan Berger
2023-07-31 21:44                     ` Limonciello, Mario
2023-07-28 19:30     ` Jarkko Sakkinen
2023-07-28 20:18       ` Daniil Stas
2023-07-31 10:14         ` Jarkko Sakkinen
2023-07-31 10:28           ` Daniil Stas
2023-07-31 11:07             ` 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=20230727200527.4080c595@g14 \
    --to=daniil.stas@posteo.net \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=Jason@zx2c4.com \
    --cc=jarkko@kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=regressions@leemhuis.info \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 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.