From: Mimi Zohar <zohar@linux.ibm.com>
To: steven chen <chenste@linux.microsoft.com>,
stefanb@linux.ibm.com, roberto.sassu@huaweicloud.com,
roberto.sassu@huawei.com, eric.snowberg@oracle.com,
ebiederm@xmission.com, paul@paul-moore.com, code@tyhicks.com,
bauermann@kolabnow.com, linux-integrity@vger.kernel.org,
kexec@lists.infradead.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: madvenka@linux.microsoft.com, nramas@linux.microsoft.com,
James.Bottomley@HansenPartnership.com, bhe@redhat.com,
vgoyal@redhat.com, dyoung@redhat.com
Subject: Re: [PATCH v7 0/7] ima: kexec: measure events between kexec load and execute
Date: Tue, 18 Feb 2025 14:39:13 -0500 [thread overview]
Message-ID: <c99d2151d3c99f86c1e4e2bbf236ad53603e2ff2.camel@linux.ibm.com> (raw)
In-Reply-To: <20250218172046.649307-1-chenste@linux.microsoft.com>
Hi Steven,
I'm ignoring this version of v7. Please remember to update the version to v8 before re-
posting and update the change log.
thanks,
Mimi
On Tue, 2025-02-18 at 09:20 -0800, steven chen wrote:
> The current kernel behavior is IMA measurements snapshot is taken at
> kexec 'load' and not at kexec 'execute'. IMA log is then carried
> over to the new kernel after kexec 'execute'.
>
> New events can be measured during/after the IMA log snapshot at kexec
> 'load' and before the system boots to the new kernel. In this scenario,
> the TPM PCRs are extended with these events, but they are not carried
> over to the new kernel after kexec soft reboot since the snapshot is
> already taken. This results in mismatch between TPM PCR quotes and the
> actual IMA measurements list after kexec soft reboot, which in turn
> results in remote attestation failure.
>
> To solve this problem -
> - allocate the necessary buffer at kexec 'load' time,
> - populate the buffer with the IMA measurements at kexec 'execute' time,
> - and measure two new IMA events 'kexec_load' and 'kexec_execute' as
> critical data to help detect missing events after kexec soft reboot.
[ ... ]
> Change Log v7:
> - Incorporated feedback from the community (Stefan Berger, Tyler Hicks)
> on v6 of this series[8].
> - Verified all the patches are bisect-safe by booting into each
> patch and verifying multiple kexec 'load' operations work,
> and also verifying kexec soft reboot works, and IMA log gets
> carried over for each patch.
prev parent reply other threads:[~2025-02-18 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 17:20 [PATCH v7 0/7] ima: kexec: measure events between kexec load and execute steven chen
2025-02-18 17:20 ` [PATCH v7 1/7] ima: define and call ima_alloc_kexec_file_buf steven chen
2025-02-18 17:20 ` [PATCH v7 2/7] kexec: define functions to map and unmap segments steven chen
2025-02-18 17:20 ` [PATCH v7 3/7] ima: kexec: skip IMA segment validation after kexec soft reboot steven chen
2025-02-18 17:20 ` [PATCH v7 4/7] ima: kexec: define functions to copy IMA log at soft boot steven chen
2025-02-18 17:20 ` [PATCH v7 5/7] ima: kexec: move IMA log copy from kexec load to execute steven chen
2025-02-18 17:20 ` [PATCH v7 6/7] ima: make the kexec extra memory configurable steven chen
2025-02-18 17:20 ` [PATCH v7 7/7] ima: measure kexec load and exec events as critical data steven chen
2025-02-18 19:39 ` Mimi Zohar [this message]
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=c99d2151d3c99f86c1e4e2bbf236ad53603e2ff2.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bauermann@kolabnow.com \
--cc=bhe@redhat.com \
--cc=chenste@linux.microsoft.com \
--cc=code@tyhicks.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=eric.snowberg@oracle.com \
--cc=kexec@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=madvenka@linux.microsoft.com \
--cc=nramas@linux.microsoft.com \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=stefanb@linux.ibm.com \
--cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).