From: steven chen <chenste@linux.microsoft.com>
To: Stefan Berger <stefanb@linux.ibm.com>,
zohar@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 v8 5/7] ima: kexec: move IMA log copy from kexec load to execute
Date: Wed, 19 Feb 2025 11:23:29 -0800 [thread overview]
Message-ID: <53a254d2-3aec-4bfa-9eca-e17f22e47b5c@linux.microsoft.com> (raw)
In-Reply-To: <7433b986-f048-494d-a66a-5888cd37b081@linux.ibm.com>
On 2/19/2025 7:57 AM, Stefan Berger wrote:
>
>
> On 2/18/25 5:55 PM, steven chen wrote:
>> ima_dump_measurement_list() is called during kexec 'load', which may
>> result in loss of IMA measurements during kexec soft reboot. It needs
>
> ... due to missed measurements that only occurred after kexec 'load'.
> Therefore, this function needs to be ...
>
>> to be called during kexec 'execute'.
>>
>> This patch includes the following changes:
>> - Implement kimage_file_post_load() function to be invoked after
>> the new
>> Kernel image has been loaded for kexec.
>
> s/Kernel/kernel
>
>> - Call kimage_file_post_load() from kexec_file_load() syscall only for
>> kexec soft reboot scenarios and not for KEXEC_FILE_ON_CRASH. It
>> will
>> map the IMA segment, and register reboot notifier for the function
>> ima_update_kexec_buffer() which would copy the IMA log at kexec soft
>> reboot.
>> - Make kexec_segment_size variable local static to the file, for it
>> to be
>
> ... to the file so that it becomes accessible ...
>
>> accessible both during kexec 'load' and 'execute'.
>> - Move ima_dump_measurement_list() call from ima_add_kexec_buffer()
>> to ima_update_kexec_buffer().
>> - Remove ima_reset_kexec_file() call from ima_add_kexec_buffer(), now
>> that the buffer is being copied at kexec 'execute', and resetting
>> the
>> file at kexec 'load' will corrupt the buffer.
>
> s/will/would
>
>>
>> Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com>
>> Signed-off-by: steven chen <chenste@linux.microsoft.com>
>
> With the above changes:
>
> Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
>
>> ---
>> kernel/kexec_file.c | 8 ++++++
>> security/integrity/ima/ima_kexec.c | 43 +++++++++++++++++++-----------
>> 2 files changed, 36 insertions(+), 15 deletions(-)
>>
>> diff --git a/kernel/kexec_file.c b/kernel/kexec_file.c
>> index 606132253c79..76b6a877b842 100644
>> --- a/kernel/kexec_file.c
>> +++ b/kernel/kexec_file.c
>> @@ -201,6 +201,11 @@ kimage_validate_signature(struct kimage *image)
>> }
>> #endif
>> +static void kimage_file_post_load(struct kimage *image)
>> +{
>> + ima_kexec_post_load(image);
>> +}
>> +
>> /*
>> * In file mode list of segments is prepared by kernel. Copy relevant
>> * data from user space, do error checking, prepare segment list
>> @@ -428,6 +433,9 @@ SYSCALL_DEFINE5(kexec_file_load, int, kernel_fd,
>> int, initrd_fd,
>> kimage_terminate(image);
>> + if (!(flags & KEXEC_FILE_ON_CRASH))
>> + kimage_file_post_load(image);
>> +
>> ret = machine_kexec_post_load(image);
>> if (ret)
>> goto out;
>> diff --git a/security/integrity/ima/ima_kexec.c
>> b/security/integrity/ima/ima_kexec.c
>> index 0fa65f91414b..f9dd7ff95b84 100644
>> --- a/security/integrity/ima/ima_kexec.c
>> +++ b/security/integrity/ima/ima_kexec.c
>> @@ -19,6 +19,7 @@
>> #ifdef CONFIG_IMA_KEXEC
>> static struct seq_file ima_kexec_file;
>> static void *ima_kexec_buffer;
>> +static size_t kexec_segment_size;
>> static bool ima_kexec_update_registered;
>> static void ima_reset_kexec_file(struct seq_file *sf)
>> @@ -129,7 +130,6 @@ void ima_add_kexec_buffer(struct kimage *image)
>> /* use more understandable variable names than defined in kbuf */
>> void *kexec_buffer = NULL;
>> size_t kexec_buffer_size = 0;
>> - size_t kexec_segment_size;
>> int ret;
>> /*
>> @@ -154,13 +154,6 @@ void ima_add_kexec_buffer(struct kimage *image)
>> return;
>> }
>> - ret = ima_dump_measurement_list(&kexec_buffer_size,
>> &kexec_buffer,
>> - kexec_segment_size);
>> - if (ret < 0) {
>> - pr_err("Failed to dump IMA measurements. Error:%d.\n", ret);
>> - return;
>> - }
>> -
>> kbuf.buffer = kexec_buffer;
>> kbuf.bufsz = kexec_buffer_size;
>> kbuf.memsz = kexec_segment_size;
>> @@ -178,12 +171,6 @@ void ima_add_kexec_buffer(struct kimage *image)
>> image->ima_segment_index = image->nr_segments - 1;
>> image->is_ima_segment_index_set = true;
>> - /*
>> - * kexec owns kexec_buffer after kexec_add_buffer() is called
>> - * and it will vfree() that buffer.
>> - */
>> - ima_reset_kexec_file(&ima_kexec_file);
>> -
>> kexec_dprintk("kexec measurement buffer for the loaded kernel
>> at 0x%lx.\n",
>> kbuf.mem);
>> }
>> @@ -194,7 +181,33 @@ void ima_add_kexec_buffer(struct kimage *image)
>> static int ima_update_kexec_buffer(struct notifier_block *self,
>> unsigned long action, void *data)
>> {
>> - return NOTIFY_OK;
>> + void *buf = NULL;
>> + size_t buf_size = 0;
>> + int ret = NOTIFY_OK;
>> +
>> + if (!kexec_in_progress) {
>> + pr_info("No kexec in progress.\n");
>> + return ret;
>> + }
>> +
>> + if (!ima_kexec_buffer) {
>> + pr_err("Kexec buffer not set.\n");
>> + return ret;
>> + }
>> +
>> + ret = ima_dump_measurement_list(&buf_size, &buf,
>> + kexec_segment_size);
>> +
>> + if (ret)
>> + pr_err("Dump measurements failed. Error:%d\n", ret);
>> +
>> + if (buf_size != 0)
>> + memcpy(ima_kexec_buffer, buf, buf_size);
>> +
>> + kimage_unmap_segment(ima_kexec_buffer);
>> + ima_kexec_buffer = NULL;
>> +
>> + return ret;
>> }
>> struct notifier_block update_buffer_nb = {
Hi Stefan, thanks for your comments. I will update in next version.
next prev parent reply other threads:[~2025-02-19 19:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 22:54 [PATCH v8 0/7] ima: kexec: measure events between kexec load and execute steven chen
2025-02-18 22:54 ` [PATCH v8 1/7] ima: define and call ima_alloc_kexec_file_buf steven chen
2025-02-20 14:53 ` Mimi Zohar
2025-02-20 15:04 ` James Bottomley
2025-02-20 16:23 ` Mimi Zohar
2025-02-21 21:02 ` steven chen
2025-02-18 22:54 ` [PATCH v8 2/7] kexec: define functions to map and unmap segments steven chen
2025-02-20 0:53 ` kernel test robot
2025-02-20 17:22 ` Mimi Zohar
2025-02-21 21:05 ` steven chen
2025-02-24 6:14 ` Baoquan He
2025-02-24 23:05 ` steven chen
2025-02-25 0:18 ` Baoquan He
2025-02-25 18:35 ` steven chen
2025-02-26 0:39 ` Baoquan He
2025-02-27 15:41 ` Mimi Zohar
2025-02-28 5:03 ` Baoquan He
2025-03-04 16:15 ` Mimi Zohar
2025-02-18 22:54 ` [PATCH v8 3/7] ima: kexec: skip IMA segment validation after kexec soft reboot steven chen
2025-02-21 15:41 ` Mimi Zohar
2025-02-21 21:06 ` steven chen
2025-02-18 22:54 ` [PATCH v8 4/7] ima: kexec: define functions to copy IMA log at soft boot steven chen
2025-02-19 15:37 ` Stefan Berger
2025-02-19 19:21 ` steven chen
2025-02-21 19:07 ` Mimi Zohar
2025-02-21 19:41 ` Stefan Berger
2025-02-18 22:55 ` [PATCH v8 5/7] ima: kexec: move IMA log copy from kexec load to execute steven chen
2025-02-19 15:57 ` Stefan Berger
2025-02-19 19:23 ` steven chen [this message]
2025-02-20 1:35 ` kernel test robot
2025-02-18 22:55 ` [PATCH v8 6/7] ima: make the kexec extra memory configurable steven chen
2025-02-20 21:36 ` Mimi Zohar
2025-02-18 22:55 ` [PATCH v8 7/7] ima: measure kexec load and exec events as critical data steven chen
2025-02-19 16:23 ` Stefan Berger
2025-02-19 19:24 ` steven chen
2025-02-21 0:46 ` Mimi Zohar
2025-02-21 21:10 ` 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=53a254d2-3aec-4bfa-9eca-e17f22e47b5c@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;
as well as URLs for NNTP newsgroup(s).