linux-kernel - Re: [PATCH v2 stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19

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] [day] [month] [year] [list]

Message-ID: <YzmwKxYVDSWsaPCU@kroah.com>
Date:   Sun, 2 Oct 2022 17:37:15 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     wangyong <yongw.pur@...il.com>
Cc:     jaewon31.kim@...sung.com, linux-kernel@...r.kernel.org,
        mhocko@...nel.org, stable@...r.kernel.org, wang.yong12@....com.cn
Subject: Re: [PATCH v2 stable-4.19 0/3] page_alloc: consider highatomic
 reserve in watermark fast backports to 4.19

On Sun, Sep 25, 2022 at 03:35:26AM -0700, wangyong wrote:
> Here are the corresponding backports to 4.19.
> And fix classzone_idx context differences causing patch merge conflicts.
> 
> Original commit IDS:
> 	3334a45 mm/page_alloc: use ac->high_zoneidx for classzone_idx
> 	f27ce0e page_alloc: consider highatomic reserve in watermark fast
> 	9282012 page_alloc: fix invalid watermark check on a negative value
> 
> Changes from v1:
> - Add commit information of the original patches.

None of these have your signed-off-by on them showing that the backport
came from you and that you are responsible for them.

So even if we did think they were valid to backport, I can't take them
as-is :(

thanks,

greg k-h