From: Mimi Zohar <zohar@linux.ibm.com>
To: steven chen <chenste@linux.microsoft.com>, Baoquan He <bhe@redhat.com>
Cc: 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 3/9] kexec: define functions to map and unmap segments
Date: Mon, 21 Apr 2025 17:35:11 -0400 [thread overview]
Message-ID: <6c3aca6815edf25828bad6f0b4587a040ada03c5.camel@linux.ibm.com> (raw)
In-Reply-To: <a9e3713f-4edf-479c-8be1-fe5b3dc22866@linux.microsoft.com>
On Mon, 2025-04-21 at 13:40 -0700, steven chen wrote:
> On 4/21/2025 7:18 AM, Mimi Zohar wrote:
> > On Mon, 2025-04-21 at 09:51 -0400, Mimi Zohar wrote:
> > > On Fri, 2025-04-18 at 12:36 +0800, Baoquan He wrote:
> > > > On 04/15/25 at 07:10pm, steven chen wrote:
> > > > > From: Steven Chen <chenste@linux.microsoft.com>
> > > > ^^^^^^
> > > As James Bottomley previously explained[1], if you haven't made any changes to
> > > Tushar's patch, then the very first line of the patch description would be
> > > "From: Tushar Sugandhi <tusharsu@linux.microsoft.com>" followed by a blank line.
> > > If there is a minor change, you would add "<your email address>: explanation".
> > > For example:
> > >
> > > Steven Chen <chenste@linux.microsoft.com>: modified patch description
> > To clarify: This line would be included below with your Signed-off-by tag.
> >
> > > [1]
> > > https://lore.kernel.org/lkml/58e70121aaee33679ac295847197c1e5511b2a81.camel@HansenPartnership.com/
> > >
> > > > > Implement kimage_map_segment() to enable IMA to map the measurement log
> > > > > list to the kimage structure during the kexec 'load' stage. This function
> > > > > gathers the source pages within the specified address range, and maps them
> > > > > to a contiguous virtual address range.
> > > > >
> > > > > This is a preparation for later usage.
> > > > >
> > > > > Implement kimage_unmap_segment() for unmapping segments using vunmap().
> > > > >
> > > > > From: Tushar Sugandhi <tusharsu@linux.microsoft.com>
> > > > ^^^^^^
> > > Neither "Author:" nor "From:" belong here. Please remove.
> > >
> > > > > Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com>
> > > > ^^^^^^^
> > > Having Tushar's "Signed-off-by" tag and yours below indicate that you modified
> > > the original author's patch.
> > To clarify: "Just" having Tushar's "Signed-off-by" tag and yours below indicate
> > that you modified the original author's patch.
>
> Hi Mimi,
>
> I will update it in next version.
Sigh, after reviewing your discussion with Baoquan, I'm not sure whether my
comment this morning added more confusion.
Option 1: Include a single "From:" line at the very top to change the author
from yourself to someone else. The following from line would make Tushar the
patch author: From: Tushar Sugandhi <tusharsu@linux.microsoft.com>
In addition, any minor changes you made should be added before your Signed-off-
by tag. For example: Steven Chen <chenste@linux.microsoft.com>: modified patch
description
Option 2: As mentioned previously and now discussed with Baoquan, adding "Co-
developed-by:"
>
> Just wandering are you done reviewing or still need more time?
Yes, I just finished reviewing/testing. The patch descriptions are looking much
better. As Baoquan reminded you, please remember to update the "ima: define and
call ima_alloc_kexec_file_buf()" patch description.
thanks,
Mimi
>
> > > > > 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>
> > > > ^^^^^
> > > >
> > > > The signing on this patch is a little confusing. I can't see who is the
> > > > real author, who is the co-author, between you and Tushar. You may need
> > > > to refer to Documentation/process/5.Posting.rst to make that clear.
> > > >
> > > > > Acked-by: Baoquan He <bhe@redhat.com>
next prev parent reply other threads:[~2025-04-21 21:35 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 [this message]
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
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=6c3aca6815edf25828bad6f0b4587a040ada03c5.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).