linux-kernel - Re: [REGRESSION] suspend to ram fails in 6.1 due to tpm errors

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 28 Nov 2022 13:03:31 +0100
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Vlastimil Babka <vbabka@...e.cz>
Cc:     Peter Huewe <peterhuewe@....de>,
        Jarkko Sakkinen <jarkko@...nel.org>,
        Jason Gunthorpe <jgg@...pe.ca>, Jan Dabros <jsd@...ihalf.com>,
        regressions@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>,
        linux-integrity@...r.kernel.org,
        Dominik Brodowski <linux@...inikbrodowski.net>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [REGRESSION] suspend to ram fails in 6.1 due to tpm errors

Hi Vlastimil,

Thanks for CC'ing me.

On Mon, Nov 28, 2022 at 09:15:33AM +0100, Vlastimil Babka wrote:
> Dominik on IRC pointed me to commit b006c439d58d ("hwrng: core - start hwrng
> kthread also for untrusted sources"), which could make sense if the TPM was not
> used at all before and now it's used for randomness. But then it probably "just"
> uncovered a pre-existing issue? Maybe there's a race with getting the randomness
> and suspend? Could it be exactly what this patch is attempting to fix?
> https://lore.kernel.org/all/20221103145450.1409273-2-jsd@semihalf.com/

The commit you referenced just turns on some functionality that most
people previously didn't have (but maybe could have, manually). So this
is a case of a new commit unearthing a bug in some old code. We had
something similar happen with a raspi driver and fixed the bug there.
>From the looks of the lore link you provided, it sounds like the same
thing has happened already there to tpm? That this is already fixed by
that commit? I think if you have a system that's readily exhibiting the
issue, the best thing to do would be to try that series, and report
back, maybe even providing your `Tested-by:` line if it works.

I'll play around and see if I can repro too. Looks like you have a T460?
I don't have exactly that but maybe something close enough.

Jason