public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jiri Slaby" <jirislaby@kernel.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: "Peter Hüwe" <PeterHuewe@gmx.de>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	linux-integrity@vger.kernel.org,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>
Subject: Re: TPM/EFI issue [Was: Linux 6.12]
Date: Sat, 30 Nov 2024 04:49:36 +0200	[thread overview]
Message-ID: <D5Z66HQJNNNL.1CPU2KF13269F@kernel.org> (raw)
In-Reply-To: <9c893c52-e960-4f30-98ce-ba7d873145bb@kernel.org>

On Wed Nov 27, 2024 at 8:46 AM EET, Jiri Slaby wrote:
> Cc TPM + EFI guys.
>
> On 17. 11. 24, 23:26, Linus Torvalds wrote:
> > But before the merge window opens, please give this a quick test to
> > make sure we didn't mess anything up. The shortlog below gives you the
> > summary for the last week, and nothing really jumps out at me. A
> > number of last-minute reverts, and some random fairly small fixes
> > fairly spread out in the tree.
>
> Hi,
>
> there is a subtle bug in 6.12 wrt TPM (in TPM, EFI, or perhaps in 
> something else):
> https://bugzilla.suse.com/show_bug.cgi?id=1233752
>
> Our testing (openQA) fails with 6.12:
> https://openqa.opensuse.org/tests/4657304#step/trup_smoke/26
>
> The last good is with 6.11.7:
> https://openqa.opensuse.org/tests/4648526
>
> In sum:
> TPM is supposed to provide a key for decrypting the root partitition, 
> but fails for some reason.
>
> It's extremely hard (so far) to reproduce outside of openQA (esp. when 
> trying custom kernels).
>
> Most of the 6.12 TPM stuff already ended in (good) 6.11.7. I tried to 
> revert:
>    423893fcbe7e tpm: Disable TPM on tpm2_create_primary() failure
> from 6.12 but that still fails.
>
> We are debugging this further, this is just so you know.
>
> Or maybe you have some immediate ideas?

Nothing immediate but I've had to tweak quite a lot of TPM bus
integrity protection feature so it is a possibility that I've
made a mistake in a point or another.

Can you bisect the issue possibly?

PS. I'm travelling next week in Spain so next time I can debug
the issue is +1 week from now (just so that you know).

BR, Jarkko

  parent reply	other threads:[~2024-11-30  2:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-17 22:26 Linux 6.12 Linus Torvalds
2024-11-19  8:48 ` Build regressions/improvements in v6.12 Geert Uytterhoeven
2024-11-19  8:52   ` Geert Uytterhoeven
2024-11-20 15:29 ` Linux 6.12 Frank Scheiner
2024-11-27  6:46 ` TPM/EFI issue [Was: Linux 6.12] Jiri Slaby
2024-11-27 16:24   ` James Bottomley
2024-11-28  7:20     ` Jiri Slaby
2024-11-28 16:13       ` James Bottomley
2024-11-29  6:36         ` Jiri Slaby
2024-11-29 16:03           ` James Bottomley
2024-11-29 21:08             ` James Bottomley
2024-12-02  7:56               ` Jiri Slaby
2024-11-30  7:52             ` Jiri Slaby
2024-11-30  2:49   ` Jarkko Sakkinen [this message]
2024-11-30  2:52     ` Jarkko Sakkinen
2024-12-02  7:52     ` Jiri Slaby
2024-12-07 12:16       ` Jarkko Sakkinen
2024-12-09  6:43         ` Jiri Slaby
2024-12-09 12:54         ` Jarkko Sakkinen
2024-12-10  6:13           ` Jiri Slaby
2024-12-10 13:04             ` James Bottomley
2024-12-14  3:54               ` 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=D5Z66HQJNNNL.1CPU2KF13269F@kernel.org \
    --to=jarkko@kernel.org \
    --cc=PeterHuewe@gmx.de \
    --cc=ardb@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=jirislaby@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox