linux-kernel - Re: [PATCH] mm: memcontrol: protect the memory in cgroup from being oom killed

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: <fd28321c-5f00-ba94-daed-2b8da2292c1f@gmail.com>
Date:   Wed, 30 Nov 2022 15:41:37 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     chengkaitao <pilgrimtao@...il.com>, tj@...nel.org,
        lizefan.x@...edance.com, hannes@...xchg.org, corbet@....net,
        mhocko@...nel.org, roman.gushchin@...ux.dev, shakeelb@...gle.com,
        akpm@...ux-foundation.org, songmuchun@...edance.com
Cc:     cgel.zte@...il.com, ran.xiaokai@....com.cn,
        viro@...iv.linux.org.uk, zhengqi.arch@...edance.com,
        ebiederm@...ssion.com, Liam.Howlett@...cle.com,
        chengzhihao1@...wei.com, haolee.swjtu@...il.com, yuzhao@...gle.com,
        willy@...radead.org, vasily.averin@...ux.dev, vbabka@...e.cz,
        surenb@...gle.com, sfr@...b.auug.org.au, mcgrof@...nel.org,
        sujiaxun@...ontech.com, feng.tang@...el.com,
        cgroups@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-mm@...ck.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] mm: memcontrol: protect the memory in cgroup from being
 oom killed

On 11/30/22 14:01, chengkaitao wrote:
> From: chengkaitao <pilgrimtao@...il.com>
> 

Yikes! Another patch from ZTE guys.

I'm suspicious to patches sent from them due to bad reputation with
kernel development community. First, they sent all patches via
cgel.zte@...il.com (listed in Cc) but Greg can't sure these are really
sent from them ([1] & [2]). Then they tried to workaround by sending
from their personal Gmail accounts, again with same response from him
[3]. And finally they sent spoofed emails (as he pointed out in [4]) -
they pretend to send from ZTE domain but actually sent from their
different domain (see raw message and look for X-Google-Original-From:
header.

I was about to review documentation part of this patch, but due to
concerns above, I have to write this reply instead. So I'm not going
to review, sorry for inconvenience.

PS: Adding Greg to Cc: list.

[1]: https://lore.kernel.org/lkml/Yw94xsOp6gvdS0UF@kroah.com/
[2]: https://lore.kernel.org/lkml/Yylv5hbSBejJ58nt@kroah.com/
[3]: https://lore.kernel.org/lkml/Y1EVnZS9BalesrC1@kroah.com/
[4]: https://lore.kernel.org/lkml/Y3NrBvIV7lH2GrWz@kroah.com/

-- 
An old man doll... just what I always wanted! - Clara