From: Jiri Slaby <jirislaby@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Peter Hüwe" <PeterHuewe@gmx.de>,
"Jarkko Sakkinen" <jarkko@kernel.org>,
"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 08:52:00 +0100 [thread overview]
Message-ID: <144c7ba3-786d-4bca-bca7-f02781c82caf@kernel.org> (raw)
In-Reply-To: <02060553aafac7e145e96510a66a6845d389d6ff.camel@HansenPartnership.com>
On 29. 11. 24, 17:03, James Bottomley wrote:
>> But well, fs/fat/ received no significant changes either.
>
> We don't use that at all in the EFI stub (and neither does systemd-
> boot). We use the protocols EFI provides to read fat volumes, so any
> issue would be in the edk2 (or in your case ovmf) FatPkg.
Sure, I had an FS corruption (during initrd write) in my mind.
--
js
suse labs
next prev parent reply other threads:[~2024-11-30 7:52 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 [this message]
2024-11-30 2:49 ` Jarkko Sakkinen
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=144c7ba3-786d-4bca-bca7-f02781c82caf@kernel.org \
--to=jirislaby@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=PeterHuewe@gmx.de \
--cc=ardb@kernel.org \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--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
all inboxes | Powered by JetHome®