Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v7 1/7] ima: define and call ima_alloc_kexec_file_buf
Date: Thu, 06 Feb 2025 11:49:48 -0500	[thread overview]
Message-ID: <4d258641d36088b1a1239724a2951211159d81f0.camel@linux.ibm.com> (raw)
In-Reply-To: <20250203232033.64123-2-chenste@linux.microsoft.com>

Thanks, Steven, for picking up and working on Tushar's patch set.

I normally finish reviewing the patch set, before commenting.  In this case, there's
a generic comment that relates to all of the patches.  It's also a way of letting you
know that I've started reviewing the patch set.  The remaining comments will come
after I finish reviewing the patch set.

On Mon, 2025-02-03 at 15:20 -0800, steven chen wrote:
> Carrying the IMA measurement list across kexec requires allocating a
> buffer and copying the measurement records.  Separate allocating the
> buffer and copying the measurement records into separate functions in
> order to allocate the buffer at kexec 'load' and copy the measurements
> at kexec 'execute'.
> 
> This patch includes the following changes:
>  - Refactor ima_dump_measurement_list() to move the memory allocation
>    to a separate function ima_alloc_kexec_file_buf() which allocates
>    buffer of size 'kexec_segment_size' at kexec 'load'.
>  - Make the local variable ima_kexec_file in ima_dump_measurement_list()
>    a local static to the file, so that it can be accessed from 
>    ima_alloc_kexec_file_buf(). Compare actual memory required to ensure 
>    there is enough memory for the entire measurement record.
>  - Copy as many measurement events as possible.
>  - Make necessary changes to the function ima_add_kexec_buffer() to call
>    the above two functions.
>  - Compared the memory size allocated with memory size of the entire 
>    measurement record. If there is not enough memory, it will copy as many
>    IMA measurement records as possible, and this situation will result
>    in a failure of remote attestation.
> 
> Author: Tushar Sugandhi <tusharsu@linux.microsoft.com>

I understand you want to credit Tushar for the patch, but the mechanism is described
in Documentation/process/submitting-patches.rst.  Refer to the paragraph on "Co-
developed-by".  There is no tag named "Author".

> Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
> Suggested-by: Mimi Zohar <zohar@linux.ibm.com>

"Suggested-by" goes before the Signed-off-by tag(s). "Reviewed-by" tag goes after
your and/or Tushar's Signed-off-tag.

> Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com>
> Signed-off-by: steven chen <chenste@linux.microsoft.com>

Before the "Co-developed-by" tag was defined, it was implied simply by this ordering
of the "Signed-off-by" tags.

For those patches you didn't modify, simply import Tushar's patch with him as the
author and add your Signed-off-by tag after his.

thanks,

Mimi


  reply	other threads:[~2025-02-06 16:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 23:20 [PATCH v7 0/7] ima: kexec: measure events between kexec load and excute steven chen
2025-02-03 23:20 ` [PATCH v7 1/7] ima: define and call ima_alloc_kexec_file_buf steven chen
2025-02-06 16:49   ` Mimi Zohar [this message]
2025-02-07 19:20     ` steven chen
2025-02-07 19:36     ` Mimi Zohar
2025-02-07 19:10   ` Mimi Zohar
2025-02-07 19:23     ` steven chen
2025-02-03 23:20 ` [PATCH v7 2/7] kexec: define functions to map and unmap segments steven chen
2025-02-07 19:15   ` Mimi Zohar
2025-02-10 17:06     ` steven chen
2025-02-12 13:03       ` Mimi Zohar
2025-02-18  4:24         ` Baoquan He
2025-02-03 23:20 ` [PATCH v7 3/7] ima: kexec: skip IMA segment validation after kexec soft reboot steven chen
2025-02-04 19:39   ` Stefan Berger
2025-02-04 20:28     ` steven chen
2025-02-04 22:51       ` Stefan Berger
2025-02-07 19:24     ` steven chen
2025-02-03 23:20 ` [PATCH v7 4/7] ima: kexec: define functions to copy IMA log at soft boot steven chen
2025-02-03 23:20 ` steven chen
2025-02-03 23:20 ` [PATCH v7 5/7] ima: kexec: move IMA log copy from kexec load to execute steven chen
2025-02-03 23:20 ` [PATCH v7 6/7] ima: make the kexec extra memory configurable steven chen
2025-02-07 16:04   ` Mimi Zohar
2025-02-03 23:20 ` [PATCH v7 7/7] ima: measure kexec load and exec events as critical data steven chen
2025-02-07 15:16   ` Mimi Zohar
2025-02-07 17:06     ` Mimi Zohar
2025-02-07 17:48       ` Stefan Berger
2025-02-07 19:26         ` steven chen
  -- strict thread matches above, loose matches on Subject: below --
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-03 18:45 [PATCH v7 0/7] ima: kexec: measure events between kexec load and excute steven chen
2025-02-03 18:45 ` [PATCH v7 1/7] ima: define and call ima_alloc_kexec_file_buf steven chen
2025-02-03 18:42 [PATCH v7 0/7] ima: kexec: measure events between kexec load and excute steven chen
2025-02-03 18:42 ` [PATCH v7 1/7] ima: define and call ima_alloc_kexec_file_buf 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=4d258641d36088b1a1239724a2951211159d81f0.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bauermann@kolabnow.com \
    --cc=chenste@linux.microsoft.com \
    --cc=code@tyhicks.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 \
    /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