linux-kernel - Re: [PATCH 5.10 140/215] mm,hwpoison: return -EBUSY when migration fails

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: <a5539a09-7964-c188-8e58-5173eb587a24@redhat.com>
Date:   Fri, 16 Jul 2021 11:59:25 +0200
From:   David Hildenbrand <david@...hat.com>
To:     Pavel Machek <pavel@....cz>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Oscar Salvador <osalvador@...e.de>,
        Naoya Horiguchi <naoya.horiguchi@....com>,
        Vlastimil Babka <vbabka@...e.cz>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Hanjun Guo <guohanjun@...wei.com>
Subject: Re: [PATCH 5.10 140/215] mm,hwpoison: return -EBUSY when migration
 fails

On 16.07.21 11:52, Pavel Machek wrote:
> Hi!
> 
>> From: Oscar Salvador <osalvador@...e.de>
>>
>> commit 3f4b815a439adfb8f238335612c4b28bc10084d8
> 
> Another format of marking upstream commits. How are this is number 8
> or so. I have scripts trying to parse this, and I don't believe I'm
> the only one.
> 
>> Link: https://lkml.kernel.org/r/20201209092818.30417-1-osalvador@suse.de
>> Signed-off-by: Oscar Salvador <osalvador@...e.de>
>> Acked-by: Naoya Horiguchi <naoya.horiguchi@....com>
>> Acked-by: Vlastimil Babka <vbabka@...e.cz>
>> Cc: David Hildenbrand <david@...hat.com>
>> Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
>> Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>
> 
> Could se simply place Upstream: <hash> tag here? That should
> discourage such "creativity"... plus it will make it clear who touched
> patch in mainline context and who in stable context.

This is properly documented

https://www.kernel.org/doc/html/v5.14-rc1//process/stable-kernel-rules.html


"
The upstream commit ID must be specified with a separate line above the 
commit text, like this:

commit <sha1> upstream.
"

-- 
Thanks,

David / dhildenb