From: steven chen <chenste@linux.microsoft.com>
To: Baoquan He <bhe@redhat.com>, Stefan Berger <stefanb@linux.ibm.com>
Cc: 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, madvenka@linux.microsoft.com,
nramas@linux.microsoft.com,
James.Bottomley@hansenpartnership.com, vgoyal@redhat.com,
dyoung@redhat.com
Subject: Re: [PATCH v10 1/8] ima: rename variable the ser_file "file" to "ima_kexec_file"
Date: Fri, 21 Mar 2025 09:15:43 -0700 [thread overview]
Message-ID: <b8882b36-e3ef-424e-9dc1-564e3d1944f9@linux.microsoft.com> (raw)
In-Reply-To: <Z9ovT3CnxBqN+cKI@MiWiFi-R3L-srv>
On 3/18/2025 7:43 PM, Baoquan He wrote:
> On 03/18/25 at 11:10am, Stefan Berger wrote:
>>
>> On 3/17/25 9:04 PM, steven chen wrote:
>>> The name of the local variable "file" of type seq_file defined in the
>>> ima_dump_measurement_list function is too generic. To better reflect the
>>> purpose of the variable, rename it to "ima_kexec_file". This change will
>>> help improve code readability and maintainability by making the variable's
>>> role more explicit.
>>>
>>> The variable ima_kexec_file is indeed the memory allocated for copying IMA
>>> measurement records. The ima_dump_measurement_list function calculates the
>>> actual memory occupied by the IMA logs and compares it with the allocated
>>> memory. If there is enough memory, it copies all IMA measurement records;
>>> otherwise, it does not copy any records, which would result in a failure
>>> of remote attestation.
>>>
>>> Suggested-by: Mimi Zohar <zohar@linux.ibm.com>
>>> Signed-off-by: steven chen <chenste@linux.microsoft.com>
>>
>>> ---
>>> security/integrity/ima/ima_kexec.c | 39 ++++++++++++++++++------------
>>> 1 file changed, 24 insertions(+), 15 deletions(-)
>>>
>>> diff --git a/security/integrity/ima/ima_kexec.c b/security/integrity/ima/ima_kexec.c
>>> index 9d45f4d26f73..8567619889d1 100644
>>> --- a/security/integrity/ima/ima_kexec.c
>>> +++ b/security/integrity/ima/ima_kexec.c
>>> @@ -15,33 +15,41 @@
>>> #include "ima.h"
>>> #ifdef CONFIG_IMA_KEXEC
>>> +/*
>>> + * Copy the measurement list to the allocated memory
>>> + * compare the size of IMA measurement list with the size of the allocated memory
>> Compare the size of the IMA ... memory.
>>
>>
>>> + * if the size of the allocated memory is not less than the size of IMA measurement list
>>> + * copy the measurement list to the allocated memory.
>>> + * else
>>> + * return error
>> If the size of the allocated memory is not less than the size of IMA
>> measurement list, copy the measurement list to the allocated memory, return
>> an error otherwise.
> Ack the suggested change.
Thanks for the comments.
next prev parent reply other threads:[~2025-03-21 16:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 1:04 [PATCH v10 0/8] ima: kexec: measure events between kexec load and execute steven chen
2025-03-18 1:04 ` [PATCH v10 1/8] ima: rename variable the ser_file "file" to "ima_kexec_file" steven chen
2025-03-18 15:10 ` Stefan Berger
2025-03-19 2:43 ` Baoquan He
2025-03-21 16:15 ` steven chen [this message]
2025-03-19 13:42 ` Mimi Zohar
2025-03-21 16:16 ` steven chen
2025-03-18 1:04 ` [PATCH v10 2/8] ima: define and call ima_alloc_kexec_file_buf() steven chen
2025-03-19 8:09 ` Baoquan He
2025-03-19 16:27 ` Mimi Zohar
2025-03-20 1:51 ` Baoquan He
2025-03-20 13:06 ` Mimi Zohar
2025-03-21 16:18 ` steven chen
2025-03-18 1:04 ` [PATCH v10 3/8] kexec: define functions to map and unmap segments steven chen
2025-03-19 10:12 ` Baoquan He
2025-03-18 1:04 ` [PATCH v10 4/8] ima: kexec: skip IMA segment validation after kexec soft reboot steven chen
2025-03-19 10:16 ` Baoquan He
2025-03-18 1:04 ` [PATCH v10 5/8] ima: kexec: define functions to copy IMA log at soft boot steven chen
2025-03-18 1:04 ` [PATCH v10 6/8] ima: kexec: move IMA log copy from kexec load to execute steven chen
2025-03-19 20:53 ` Mimi Zohar
2025-03-21 16:20 ` steven chen
2025-03-20 2:06 ` Baoquan He
2025-03-21 16:23 ` steven chen
2025-03-24 11:00 ` Baoquan He
2025-03-25 22:27 ` steven chen
2025-03-26 2:27 ` Baoquan He
2025-03-26 22:46 ` steven chen
2025-03-26 23:44 ` Mimi Zohar
2025-03-18 1:04 ` [PATCH v10 7/8] ima: make the kexec extra memory configurable steven chen
2025-03-20 2:52 ` Baoquan He
2025-03-21 16:46 ` steven chen
2025-03-18 1:04 ` [PATCH v10 8/8] ima: measure kexec load and exec events as critical data steven chen
2025-03-20 2:59 ` Mimi Zohar
2025-03-21 16:49 ` 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=b8882b36-e3ef-424e-9dc1-564e3d1944f9@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).