linux-kernel - Re: [PATCH v8 1/7] ima: define and call ima_alloc_kexec_file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0e82335b-ef66-46bf-a0b8-211e20fff77a@linux.microsoft.com>
Date: Fri, 21 Feb 2025 13:02:58 -0800
From: steven chen <chenste@...ux.microsoft.com>
To: Mimi Zohar <zohar@...ux.ibm.com>,
 James Bottomley <James.Bottomley@...senPartnership.com>,
 stefanb@...ux.ibm.com, roberto.sassu@...weicloud.com,
 roberto.sassu@...wei.com, eric.snowberg@...cle.com, ebiederm@...ssion.com,
 paul@...l-moore.com, code@...icks.com, bauermann@...abnow.com,
 linux-integrity@...r.kernel.org, kexec@...ts.infradead.org,
 linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: madvenka@...ux.microsoft.com, nramas@...ux.microsoft.com, bhe@...hat.com,
 vgoyal@...hat.com, dyoung@...hat.com
Subject: Re: [PATCH v8 1/7] ima: define and call ima_alloc_kexec_file_buf

On 2/20/2025 8:23 AM, Mimi Zohar wrote:
> On Thu, 2025-02-20 at 10:04 -0500, James Bottomley wrote:
>> On Thu, 2025-02-20 at 09:53 -0500, Mimi Zohar wrote:
>>> On Tue, 2025-02-18 at 14:54 -0800, steven chen wrote:
>> [...
>>>> Author: Tushar Sugandhi <tusharsu@...ux.microsoft.com>
>>> Steven, thank you again for picking up this patch set.
>>>
>>> As previously explained, there is no tag named "Author" in
>>> https://www.kernel.org/doc/Documentation/process/submitting-patches.rst
>>> .  To give credit to the original author use "Co-developed-by".
>> Just on this, only use the co-developed-by if you actually *modified*
>> the patch.  If you're just transmitting the patch unmodified you can
>> give original author credit by including a
>>
>> From: original author <email>
>>
>> Followed by a blank line at the beginning of the email.  That makes the
>> git author field contan whatever the From: line says.  You still need a
>> signoff from yourself in the original patch because you transmitted it.
>>
>> Some people also consider minor modifications to be insufficient to
>> disturb the original copyright ownership and simply document what they
>> did in square brackets under their signoff, like this:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b5d1e6ee761a109400e97ac6a1b91c57d0f6a43a
> Originally I had said:
>
>     > Signed-off-by: Tushar Sugandhi <tusharsu@...ux.microsoft.com>
>     > Signed-off-by: steven chen <chenste@...ux.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, James, for the explanation of using "From: original author <email>" to force the
> author to be Tushar.
>
> Mimi

Thanks, I will update in next version.