From: Bagas Sanjaya <bagasdotme@gmail.com>
To: chengkaitao <pilgrimtao@gmail.com>,
tj@kernel.org, lizefan.x@bytedance.com, hannes@cmpxchg.org,
corbet@lwn.net, mhocko@kernel.org, roman.gushchin@linux.dev,
shakeelb@google.com, akpm@linux-foundation.org,
songmuchun@bytedance.com
Cc: cgel.zte@gmail.com, ran.xiaokai@zte.com.cn,
viro@zeniv.linux.org.uk, zhengqi.arch@bytedance.com,
ebiederm@xmission.com, Liam.Howlett@Oracle.com,
chengzhihao1@huawei.com, haolee.swjtu@gmail.com,
yuzhao@google.com, willy@infradead.org, vasily.averin@linux.dev,
vbabka@suse.cz, surenb@google.com, sfr@canb.auug.org.au,
mcgrof@kernel.org, sujiaxun@uniontech.com, feng.tang@intel.com,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] mm: memcontrol: protect the memory in cgroup from being oom killed
Date: Wed, 30 Nov 2022 15:41:37 +0700 [thread overview]
Message-ID: <fd28321c-5f00-ba94-daed-2b8da2292c1f@gmail.com> (raw)
In-Reply-To: <20221130070158.44221-1-chengkaitao@didiglobal.com>
On 11/30/22 14:01, chengkaitao wrote:
> From: chengkaitao <pilgrimtao@gmail.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@gmail.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
next prev parent reply other threads:[~2022-11-30 8:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 7:01 [PATCH] mm: memcontrol: protect the memory in cgroup from being oom killed chengkaitao
2022-11-30 8:41 ` Bagas Sanjaya [this message]
2022-11-30 11:33 ` Tao pilgrim
2022-11-30 12:43 ` Bagas Sanjaya
2022-11-30 13:25 ` 程垲涛 Chengkaitao Cheng
2022-11-30 15:46 ` 程垲涛 Chengkaitao Cheng
2022-11-30 16:27 ` Michal Hocko
2022-12-01 4:52 ` 程垲涛 Chengkaitao Cheng
2022-12-01 7:49 ` 程垲涛 Chengkaitao Cheng
2022-12-01 9:02 ` Michal Hocko
2022-12-01 13:05 ` 程垲涛 Chengkaitao Cheng
2022-12-01 8:49 ` Michal Hocko
2022-12-01 10:52 ` 程垲涛 Chengkaitao Cheng
2022-12-01 12:44 ` Michal Hocko
2022-12-01 13:08 ` Michal Hocko
2022-12-01 14:30 ` 程垲涛 Chengkaitao Cheng
2022-12-01 15:17 ` Michal Hocko
2022-12-02 8:37 ` 程垲涛 Chengkaitao Cheng
2022-11-30 13:15 ` Michal Hocko
2022-11-30 23:29 ` Roman Gushchin
2022-12-01 20:18 ` Mina Almasry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd28321c-5f00-ba94-daed-2b8da2292c1f@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cgel.zte@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=feng.tang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=haolee.swjtu@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=mcgrof@kernel.org \
--cc=mhocko@kernel.org \
--cc=pilgrimtao@gmail.com \
--cc=ran.xiaokai@zte.com.cn \
--cc=roman.gushchin@linux.dev \
--cc=sfr@canb.auug.org.au \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=sujiaxun@uniontech.com \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=vasily.averin@linux.dev \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=yuzhao@google.com \
--cc=zhengqi.arch@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).