From: Jarkko Sakkinen <jarkko@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
surenkj@amazon.com, noodles@meta.com, kernel-team@meta.com
Subject: Re: [PATCH 2/2] tpm: Disable a TPM whose hwrng reads keep failing
Date: Thu, 12 Nov 2026 00:20:28 +0200 [thread overview]
Message-ID: <avTqLMLZwKOb-Q_j@kernel.org> (raw)
In-Reply-To: <avTpOlKixInIBmE6@kernel.org>
On Thu, Nov 12, 2026 at 12:16:30AM +0200, Jarkko Sakkinen wrote:
> I'm thinking here that why not disable on first failure?
It's a more intrusive change, yes, but then again having a count
would require assumption that there is high odds e.g., for the
following scenario:
1. TPM hwrng fails.
2. TPM hwrng succeeds.
I don't this is very likely to ever happen... So thus I'd drill
this even more than you did.
Br, Jarkko
next prev parent reply other threads:[~2026-11-11 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 9:57 [PATCH 0/2] tpm: Stop retrying TPMs that have stopped working Breno Leitao
2026-11-11 9:57 ` [PATCH 1/2] tpm: Disable a TPM that stops responding Breno Leitao
2026-11-11 22:14 ` Jarkko Sakkinen
2026-11-11 9:57 ` [PATCH 2/2] tpm: Disable a TPM whose hwrng reads keep failing Breno Leitao
2026-11-11 22:16 ` Jarkko Sakkinen
2026-11-11 22:20 ` Jarkko Sakkinen [this message]
2026-11-11 22:30 ` [PATCH 0/2] tpm: Stop retrying TPMs that have stopped working Jarkko Sakkinen
2026-11-11 22:43 ` Jarkko Sakkinen
2026-11-11 22:46 ` Jarkko Sakkinen
2026-11-12 1:57 ` Jarkko Sakkinen
2026-11-12 2:01 ` Jarkko Sakkinen
2026-11-12 12:20 ` Breno Leitao
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=avTqLMLZwKOb-Q_j@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noodles@meta.com \
--cc=peterhuewe@gmx.de \
--cc=surenkj@amazon.com \
/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.