linux-kernel - Re: RFC: backport of commit a32c1c61212d

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]

Date:   Tue, 1 Sep 2020 10:09:37 -0700
From:   Doug Berger <opendmb@...il.com>
To:     Florian Fainelli <f.fainelli@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     stable@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
        Mike Rapoport <rppt@...ux.ibm.com>,
        Pavel Tatashin <pasha.tatashin@...cle.com>,
        Russell King <linux@...linux.org.uk>,
        Michal Hocko <mhocko@...nel.org>,
        Olof Johansson <olof@...om.net>,
        Zhaoyang Huang <zhaoyang.huang@...soc.com>,
        zhaoyang <huangzhaoyang@...il.com>,
        Ingo Molnar <mingo@...nel.org>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        David Hildenbrand <david@...hat.com>,
        Baoquan He <bhe@...hat.com>
Subject: Re: RFC: backport of commit a32c1c61212d

On 9/1/2020 9:36 AM, Florian Fainelli wrote:
> 
> 
> On 9/1/2020 9:06 AM, Doug Berger wrote:
>> On 9/1/2020 7:00 AM, Greg Kroah-Hartman wrote:
> 
> [snip]
> 
>> [snip]
>>
>> My best guess at this point is to submit patches to the affected stable
>> branches like the one in my RFC and reference a32c1c61212d as the
>> upstream commit. This would be confusing to anyone that tried to compare
>> the submitted patch with the upstream patch since they
>> wouldn't look at all alike, but the fixes and upstream tags would define
>> the affected range in Linus' tree.
>>
>> I would appreciate any guidance on how best to handle this kind of
>> situation.
> 
> You could submit various patches with [PATCH stable x.y] in the subject
> to indicate they are targeting a specific stable branch, copy
> stable@...r.kernel.org as well as all recipients in this email and see
> if that works.
> 
> Not sure if there is a more documented process than that.
Yes, that is what I had in mind based on the "Option 3" for patch
submission. The sticking point is this requirement:
"You must note the upstream commit ID in the changelog of your submission"

My best guess is to use a32c1c61212d, but that could easily cause
confusion in this case. My hope is that now I can reference this
discussion to provide additional clarity.

Thanks,
    Doug