linux-kernel - Re: [PATCH v3] tpm: disable hwrng for fTPM on some AMD designs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sun, 12 Mar 2023 11:40:36 +0100
From:   "Linux regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Jarkko Sakkinen <jarkko@...nel.org>,
        Linux regressions mailing list <regressions@...ts.linux.dev>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Peter Huewe <peterhuewe@....de>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Dominik Brodowski <linux@...inikbrodowski.net>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        stable@...r.kernel.org,
        James Bottomley <James.Bottomley@...senpartnership.com>,
        reach622@...lcuk.com, Bell <1138267643@...com>,
        "Jason A . Donenfeld" <Jason@...c4.com>,
        linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
        Mario Limonciello <mario.limonciello@....com>
Subject: Re: [PATCH v3] tpm: disable hwrng for fTPM on some AMD designs

On 12.03.23 02:42, Jarkko Sakkinen wrote:
> On Sun, Mar 12, 2023 at 03:35:08AM +0200, Jarkko Sakkinen wrote:
>> On Fri, Mar 10, 2023 at 06:43:47PM +0100, Thorsten Leemhuis wrote:
>>> [adding Linux to the list of recipients]
>>>
>>> On 08.03.23 10:42, Linux regression tracking (Thorsten Leemhuis) wrote:
>>>> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
>>>> for once, to make this easily accessible to everyone.
>>>>
>>>> Jarkko, thx for reviewing and picking below fix up. Are you planning to
>>>> send this to Linus anytime soon, now that the patch was a few days in
>>>> next? It would be good to get this 6.1 regression finally fixed, it
>>>> already took way longer then the time frame
>>>> Documentation/process/handling-regressions.rst outlines for a case like
>>>> this. But well, that's how it is sometimes...
>>>
>>> Linus, would you consider picking this fix up directly from here or from
>>> linux-next (8699d5244e37)? It's been in the latter for 9 days now
>>> afaics. And the issue seems to bug more than just one or two users, so
>>> it IMHO would be good to get this finally resolved.
>>>
>>> Jarkko didn't reply to my inquiry, guess something else keeps him busy.
>>
>> That's a bit arrogant. You emailed only 4 days ago.
>>
>> I'm open to do PR for rc3 with the fix, if it cannot wait to v6.4 pr.
> 
> If this is about slow response with kernel bugzilla: [...]

Not at all, I don't care if developers use bugzilla or ignore it, as
long as the regression itself it dealt with.

Fun fact: I actually wanted to get rid of bugzilla for developers/
subsystems that didn't opt-in, but then another plan came up. See
https://lwn.net/Articles/910740/

Ciao, Thorsten