From: steven chen <chenste@linux.microsoft.com>
To: Baoquan He <bhe@redhat.com>
Cc: zohar@linux.ibm.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, madvenka@linux.microsoft.com,
nramas@linux.microsoft.com,
James.Bottomley@hansenpartnership.com, vgoyal@redhat.com,
dyoung@redhat.com
Subject: Re: [PATCH v12 5/9] ima: kexec: define functions to copy IMA log at soft boot
Date: Sun, 20 Apr 2025 05:33:10 -0700 [thread overview]
Message-ID: <6a4ecd66-4249-476c-87fa-b5a3806fae5e@linux.microsoft.com> (raw)
In-Reply-To: <aAIB9ga3wPWb5sC8@MiWiFi-R3L-srv>
On 4/18/2025 12:40 AM, Baoquan He wrote:
> On 04/15/25 at 07:10pm, steven chen wrote:
>> From: Steven Chen <chenste@linux.microsoft.com>
>>
>> The IMA log is currently copied to the new kernel during kexec 'load'
>> using ima_dump_measurement_list(). However, the log copied at kexec
>> 'load' may result in loss of IMA measurements that only occurred after
>> kexec "load'. Setup the needed infrastructure to move the IMA log copy
>> from kexec 'load' to 'execute'.
>>
>> Define a new IMA hook ima_update_kexec_buffer() as a stub function.
>> It will be used to call ima_dump_measurement_list() during kexec 'execute'.
>>
>> Implement ima_kexec_post_load() function to be invoked after the new
>> Kernel image has been loaded for kexec. ima_kexec_post_load() maps the
>> IMA buffer to a segment in the newly loaded Kernel. It also registers
>> the reboot notifier_block to trigger ima_update_kexec_buffer() at
>> kexec 'execute'.
>>
>> Set the priority of register_reboot_notifier to INT_MIN to ensure that the
>> IMA log copy operation will happen at the end of the operation chain, so
>> that all the IMA measurement records extended into the TPM are copied
>>
>> Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com>
> ^^^
>
> The tag
Hi Baoquan,
I will add Co-developed-by tag in next version.
Thanks,
Steven
>> Cc: Eric Biederman <ebiederm@xmission.com>
>> Cc: Baoquan He <bhe@redhat.com>
>> Cc: Vivek Goyal <vgoyal@redhat.com>
>> Cc: Dave Young <dyoung@redhat.com>
>> Signed-off-by: Steven Chen <chenste@linux.microsoft.com>
>> Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
>> ---
>> include/linux/ima.h | 3 ++
>> security/integrity/ima/ima_kexec.c | 47 ++++++++++++++++++++++++++++++
>> 2 files changed, 50 insertions(+)
> Other than the tag, this looks good to me:
>
> Acked-by: Baoquan He <bhe@redhat.com>
>
>> diff --git a/include/linux/ima.h b/include/linux/ima.h
>> index 0bae61a15b60..8e29cb4e6a01 100644
>> --- a/include/linux/ima.h
>> +++ b/include/linux/ima.h
>> @@ -32,6 +32,9 @@ static inline void ima_appraise_parse_cmdline(void) {}
>>
>> #ifdef CONFIG_IMA_KEXEC
>> extern void ima_add_kexec_buffer(struct kimage *image);
>> +extern void ima_kexec_post_load(struct kimage *image);
>> +#else
>> +static inline void ima_kexec_post_load(struct kimage *image) {}
>> #endif
>>
>> #else
>> diff --git a/security/integrity/ima/ima_kexec.c b/security/integrity/ima/ima_kexec.c
>> index 7e0a19c3483f..e79f6caf895b 100644
>> --- a/security/integrity/ima/ima_kexec.c
>> +++ b/security/integrity/ima/ima_kexec.c
>> @@ -12,10 +12,14 @@
>> #include <linux/kexec.h>
>> #include <linux/of.h>
>> #include <linux/ima.h>
>> +#include <linux/reboot.h>
>> +#include <asm/page.h>
>> #include "ima.h"
>>
>> #ifdef CONFIG_IMA_KEXEC
>> +static bool ima_kexec_update_registered;
>> static struct seq_file ima_kexec_file;
>> +static void *ima_kexec_buffer;
>>
>> static void ima_free_kexec_file_buf(struct seq_file *sf)
>> {
>> @@ -162,6 +166,49 @@ void ima_add_kexec_buffer(struct kimage *image)
>> kexec_dprintk("kexec measurement buffer for the loaded kernel at 0x%lx.\n",
>> kbuf.mem);
>> }
>> +
>> +/*
>> + * Called during kexec execute so that IMA can update the measurement list.
>> + */
>> +static int ima_update_kexec_buffer(struct notifier_block *self,
>> + unsigned long action, void *data)
>> +{
>> + return NOTIFY_OK;
>> +}
>> +
>> +static struct notifier_block update_buffer_nb = {
>> + .notifier_call = ima_update_kexec_buffer,
>> + .priority = INT_MIN
>> +};
>> +
>> +/*
>> + * Create a mapping for the source pages that contain the IMA buffer
>> + * so we can update it later.
>> + */
>> +void ima_kexec_post_load(struct kimage *image)
>> +{
>> + if (ima_kexec_buffer) {
>> + kimage_unmap_segment(ima_kexec_buffer);
>> + ima_kexec_buffer = NULL;
>> + }
>> +
>> + if (!image->ima_buffer_addr)
>> + return;
>> +
>> + ima_kexec_buffer = kimage_map_segment(image,
>> + image->ima_buffer_addr,
>> + image->ima_buffer_size);
>> + if (!ima_kexec_buffer) {
>> + pr_err("Could not map measurements buffer.\n");
>> + return;
>> + }
>> +
>> + if (!ima_kexec_update_registered) {
>> + register_reboot_notifier(&update_buffer_nb);
>> + ima_kexec_update_registered = true;
>> + }
>> +}
>> +
>> #endif /* IMA_KEXEC */
>>
>> /*
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2025-04-20 12:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 2:10 [PATCH v12 0/9] ima: kexec: measure events between kexec load and execute steven chen
2025-04-16 2:10 ` [PATCH v12 1/9] ima: rename variable the seq_file "file" to "ima_kexec_file" steven chen
2025-04-18 3:30 ` Baoquan He
2025-04-16 2:10 ` [PATCH v12 2/9] ima: define and call ima_alloc_kexec_file_buf() steven chen
2025-04-18 4:33 ` Baoquan He
2025-04-20 12:22 ` steven chen
2025-04-16 2:10 ` [PATCH v12 3/9] kexec: define functions to map and unmap segments steven chen
2025-04-18 4:36 ` Baoquan He
2025-04-20 12:30 ` steven chen
2025-04-21 2:09 ` Baoquan He
2025-04-21 13:51 ` Mimi Zohar
2025-04-21 14:18 ` Mimi Zohar
2025-04-21 20:40 ` steven chen
2025-04-21 21:35 ` Mimi Zohar
2025-04-21 21:44 ` steven chen
2025-04-16 2:10 ` [PATCH v12 4/9] ima: kexec: skip IMA segment validation after kexec soft reboot steven chen
2025-04-18 7:37 ` Baoquan He
2025-04-20 12:32 ` steven chen
2025-04-16 2:10 ` [PATCH v12 5/9] ima: kexec: define functions to copy IMA log at soft boot steven chen
2025-04-18 7:40 ` Baoquan He
2025-04-20 12:33 ` steven chen [this message]
2025-04-16 2:10 ` [PATCH v12 6/9] ima: kexec: move IMA log copy from kexec load to execute steven chen
2025-04-16 2:10 ` [PATCH v12 7/9] ima: verify if the segment size has changed steven chen
2025-04-16 2:10 ` [PATCH v12 8/9] ima: make the kexec extra memory configurable steven chen
2025-04-18 8:14 ` Baoquan He
2025-04-20 13:03 ` steven chen
2025-04-16 2:10 ` [PATCH v12 9/9] ima: measure kexec load and exec events as critical data steven chen
2025-04-18 9:08 ` Baoquan He
2025-04-20 13:10 ` steven chen
2025-04-17 1:09 ` [PATCH v12 0/9] ima: kexec: measure events between kexec load and execute Stefan Berger
2025-04-20 12:21 ` steven chen
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=6a4ecd66-4249-476c-87fa-b5a3806fae5e@linux.microsoft.com \
--to=chenste@linux.microsoft.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bauermann@kolabnow.com \
--cc=bhe@redhat.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 \
--cc=zohar@linux.ibm.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