Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Stefan Berger <stefanb@linux.ibm.com>,
	Tushar Sugandhi <tusharsu@linux.microsoft.com>,
	Jonathan McDowell <noodles@fb.com>,
	bauermann@kolabnow.com
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	Alasdair G Kergon <agk@redhat.com>,
	Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
	Tyler Hicks <tyhicks@linux.microsoft.com>,
	code@tyhicks.com
Subject: Re: need help: patches to capture events between kexec load and execute
Date: Tue, 06 Jun 2023 11:59:06 -0400	[thread overview]
Message-ID: <91dd069c090522be1e3369e83520d3813336b5bf.camel@linux.ibm.com> (raw)
In-Reply-To: <3748147f-85f5-4aeb-0083-cbeef375e12a@linux.ibm.com>

On Tue, 2023-06-06 at 11:37 -0400, Stefan Berger wrote:
> 
> On 5/31/23 18:43, Mimi Zohar wrote:
> > On Wed, 2023-05-31 at 15:02 -0700, Tushar Sugandhi wrote:
> >> Hi Mimi,
> >>
> >> On 5/31/23 04:39, Mimi Zohar wrote:
> >>> Hi Tushar,
> >>>
> >>> On Thu, 2023-05-25 at 10:21 -0700, Tushar Sugandhi wrote:
> >>>
> >>>> The issue of IMA measurements getting lost between kexec 'load' and 'execute' still exists.
> >>>> I verified it on the mainline kernel 6.4.rc3. See *Appendix A* for details.
> 
> I think there's a 2nd problem.  Once the IMA measurement list is frozen (at kexec 'exec' stage)
> IMA must stop extending PCRs. It can log (into the void) if it wanted to but the PCR extensions
> have to stop otherwise the TPM's PCR state won't match the log in the kexec'ed-to kernel. I have
> seen that on PPC64 some processes are being kicked off by kexec 'exec' that end up causing TPM
> driver error message due to what seems to be a shutdown of the driver subsystem at this point.
> I am not sure what an elegant method would be to stop PCR extensions. Maybe a flag on the level
> of IMA would do? Or notifying the TPM driver to reject PCR extensions or just any command?

Thank you for raising this concern.

Agreed "kexec exec" might trigger additional measurements.  As long as
these are known, consistent measurements, they could be pre-measured
before calling "kexec exec".

-- 
thanks,

Mimi


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2023-06-06 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04  6:16 need help: patches to capture events between kexec load and execute Tushar Sugandhi
2022-06-06  8:19 ` Jonathan McDowell
2022-06-06 17:22   ` Tushar Sugandhi
     [not found]   ` <87775c1e-d1d3-519c-599b-30cdb1691cb2@linux.microsoft.com>
2023-05-31 11:39     ` Mimi Zohar
     [not found]       ` <41270374-dc5e-3aa2-d2ed-9b8fc73ad65f@linux.microsoft.com>
2023-05-31 22:43         ` Mimi Zohar
2023-06-06 15:37           ` Stefan Berger
2023-06-06 15:59             ` Mimi Zohar [this message]
2023-06-07 18:42               ` Stefan Berger

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=91dd069c090522be1e3369e83520d3813336b5bf.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=agk@redhat.com \
    --cc=bauermann@kolabnow.com \
    --cc=code@tyhicks.com \
    --cc=kexec@lists.infradead.org \
    --cc=noodles@fb.com \
    --cc=nramas@linux.microsoft.com \
    --cc=stefanb@linux.ibm.com \
    --cc=tusharsu@linux.microsoft.com \
    --cc=tyhicks@linux.microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox