All of lore.kernel.org
 help / color / mirror / Atom feed
From: jasmeet.bhatia.us@gmail.com
To: ilias.apalodimas@linaro.org
Cc: ardb@kernel.org, rafael@kernel.org, pavel@ucw.cz,
	linux-efi@vger.kernel.org, linux-pm@vger.kernel.org,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] efi/tpm: Preserve event log without changing x86 E820
Date: Fri, 20 Nov 2026 00:39:13 +0000	[thread overview]
Message-ID: <32909f9cc196a161bf380b6f64603b75@gmail.com> (raw)
In-Reply-To: <CAC_iWjJ1L5MYWy2vHG3AHYcfqx7urJmaTYP7vuyvZm8GSnWCDw@mail.gmail.com>

Hi Ilias,

On Wed Nov 18, 2026 at 10:11 PM -08:00, Ilias Apalodimas wrote:
> Hi Jasmeet,
> 
> On Wed, 18 Nov 2026 at 04:57, <jasmeet.bhatia.us@gmail.com> wrote:
> >
> > Hi Ard and Ilias,
> >
> > I wanted to follow up on this discussion after a couple of months.
> > My bad at being slow, at keep this discussion moving.
> >
> > Has there been any more considerations with the preferred approach,
> > regarding the EFI TPM event log reference and kexec?
> >
> > This issue is still relevant to Framework 16 owners and the temporary
> > fix has been confirmed to work for other users despite not being a
> > proper fix to this issue.
> >
> > I'm always happy to prepare and test any patches once we decide what
> > direction we want to move forward towards!
> 
> Ard suggested we discard the EventLog on kexecs and I agree that in
> its current state it doesn't offer much to security. Is there any
> specific reason you want it to survive?
> 

No, I don't have a specific reason to preseve the TPM event log across
kexec. My original patch only preserved it to avoid adding any
regressions, but I do agree that not preserving the event log would
simplify things greatly, and I can't think of it providing much value.

I'm hoping that will allow us to return back to the EFI_LOADER_DATA and
the E820 instability issue that was causing hibernation failures on
Framework laptops, and possibly other devices.

If you and Ard are comfortable with that approach, I'd be happy to prep
that patch and test it!

Thanks again for the guidance!

Jazz


  reply	other threads:[~2026-11-20  0:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 11:34 [PATCH v1 0/2] efi/tpm: Preserve event log without changing x86 E820 Jasmeet (Jazz) Bhatia
2026-09-01 11:34 ` [PATCH v1 1/2] efi/libstub: Install memreserve table on x86 Jasmeet (Jazz) Bhatia
2026-09-01 11:34 ` [PATCH v1 2/2] efi/tpm: Persistently reserve the TPM event log Jasmeet (Jazz) Bhatia
2026-09-03 14:18 ` [PATCH v1 0/2] efi/tpm: Preserve event log without changing x86 E820 Ard Biesheuvel
2026-09-04 15:45   ` Jasmeet (Jazz) Bhatia
2026-09-04 16:38     ` Ard Biesheuvel
2026-09-07 15:57       ` Ilias Apalodimas
2026-09-11  3:03         ` Jasmeet (Jazz) Bhatia
2026-11-18  2:57         ` jasmeet.bhatia.us
2026-11-19  6:11           ` Ilias Apalodimas
2026-11-20  0:39             ` jasmeet.bhatia.us [this message]
2026-11-20  4:01               ` dev12124

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=32909f9cc196a161bf380b6f64603b75@gmail.com \
    --to=jasmeet.bhatia.us@gmail.com \
    --cc=ardb@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rafael@kernel.org \
    --cc=x86@kernel.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 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.