From: Jarkko Sakkinen <jarkko@kernel.org>
To: David Laight <david.laight.linux@gmail.com>
Cc: Breno Leitao <leitao@debian.org>, 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 v2 2/2] tpm: Disable TPM on TPM_RC_INITIALIZE
Date: Fri, 13 Nov 2026 01:31:09 +0200 [thread overview]
Message-ID: <avZMPeUtzV3JyAX0@kernel.org> (raw)
In-Reply-To: <20261112225759.67730166@pumpkin>
On Thu, Nov 12, 2026 at 10:57:59PM +0000, David Laight wrote:
> On Thu, 12 Nov 2026 04:30:18 -0800
> Breno Leitao <leitao@debian.org> wrote:
>
> > From: Jarkko Sakkinen <jarkko@kernel.org>
> >
> > If the TPM has been spuriously disabled, the game is over. Let's reflect
> > this truth with TPM_CHIP_FLAG_DISABLE.
>
> Shouldn't it be completely 'game over'?
> (aka panic time...)
There's nothing pointing to that direction. Nothing is really broken
except likely firmware bug or similar situation. We don't want to brick
the machine because of that. Neither security is endangered as
anything that was sealed with TPM, it is inaccessible.
It's also useful for us that any possible user has a chance to run e.g.,
acpidump without kernel pulling the carpet.
>
> David
Br, Jarkko
next prev parent reply other threads:[~2026-11-12 23:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 12:30 [PATCH v2 0/2] tpm: Stop retrying TPMs that have stopped working Breno Leitao
2026-11-12 12:30 ` [PATCH v2 1/2] tpm: Disable a TPM that stops responding Breno Leitao
2026-11-12 14:00 ` Jarkko Sakkinen
2026-11-12 14:03 ` Jarkko Sakkinen
2026-11-12 15:45 ` Breno Leitao
2026-11-12 20:40 ` Breno Leitao
2026-11-12 21:07 ` Jarkko Sakkinen
2026-11-12 21:16 ` Jarkko Sakkinen
2026-11-12 12:30 ` [PATCH v2 2/2] tpm: Disable TPM on TPM_RC_INITIALIZE Breno Leitao
2026-11-12 13:37 ` Jarkko Sakkinen
2026-11-12 22:57 ` David Laight
2026-11-12 23:31 ` Jarkko Sakkinen [this message]
2026-11-12 23:39 ` 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=avZMPeUtzV3JyAX0@kernel.org \
--to=jarkko@kernel.org \
--cc=david.laight.linux@gmail.com \
--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.