From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 165A5C352A1 for ; Wed, 30 Nov 2022 11:33:17 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 734BC6B0072; Wed, 30 Nov 2022 06:33:17 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 6E3F76B0073; Wed, 30 Nov 2022 06:33:17 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 5AC006B0074; Wed, 30 Nov 2022 06:33:17 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 481B36B0072 for ; Wed, 30 Nov 2022 06:33:17 -0500 (EST) Received: from smtpin24.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay04.hostedemail.com (Postfix) with ESMTP id EDF611A0D9D for ; Wed, 30 Nov 2022 11:33:16 +0000 (UTC) X-FDA: 80189897592.24.E1D62AB Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) by imf18.hostedemail.com (Postfix) with ESMTP id 878591C000E for ; Wed, 30 Nov 2022 11:33:15 +0000 (UTC) Received: by mail-lj1-f175.google.com with SMTP id bn5so20550793ljb.2 for ; Wed, 30 Nov 2022 03:33:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=bbgF/8QJth7Q6iZLlIiOpcOOnk+o4nClIAC+d8Lf9z0=; b=cgrBYVcGGaOmhs4NUM2DMBzEteSqsnNo+s1OWAu0xrFfR8SfGHhoYWl6cON5bJQf5H kBXo+HTMLYJlc0NNqyXTeNHVsKFqrN9RnSJvYMAt9wsTzoHjoBDz54HyrId55uPzhcey WrkHDI90HmJoIfjTMzlxSFuMRM+ZEK+h+tp2CXCTYTjqjx+4Ho1p2q1qT5Xh0Pe1NIpw kh3Ph4481EH6HJsaTRzldrzwYx9ab3Q4uT9o4p32qRaA2tLn+Hf0w3FMTq1prgn3d5jp NtxVXq9wW/MEdgV2FWkhhU7TsMvsvlWqvebJsqA+xk8HaXGX4H+zuKYU5RX6czhqRUDe TW5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=bbgF/8QJth7Q6iZLlIiOpcOOnk+o4nClIAC+d8Lf9z0=; b=WDGv0ouQjY8lDBQYkTieFbhqcO3hwUpiacRkt9N4xdyQIfUzjY0DunRt8qDoeSbTn3 r9M/GidVwibZ9j6ul96RgI5fx4jnRlTuja1JejFzJPggmTDLJRSkC4yTCYyV+CEuGrFg eW1k32PNA6WDrDp/GFXoY7cgisi2dANzuNPbRSB2amnnrQ3KkqcF2NrJJjEOGQdjpY7m V3aNZ/D+csdUF/tMnQI99OApElVF5WcM4G8+16n1u848WazVJGyCMD9Gwl/RjlNmOp4U rgTxHeTNyANMpjmqpeKMxk44U0RrRdgyHPbaucn/x6IS9vP1noJ++MYomvXwfvTo+XFo ZSxQ== X-Gm-Message-State: ANoB5pnTk0VjrAf+9PabZ5UJi6rIH6QlMD3T77esKbHso/8oG05J577j Ef6pvBiAj1W8RCImflQej95z16G5+Rd4NOHf43s= X-Google-Smtp-Source: AA0mqf4DNgrzSTa3qDkcM1vR3wsA4xbwLoMawo/HYfBGJ5539OEYNPmp+YyAmqJIJYo2LXuFpOGWdNGqzEgPvVjR9QQ= X-Received: by 2002:a2e:3815:0:b0:279:8c75:b1a8 with SMTP id f21-20020a2e3815000000b002798c75b1a8mr8432976lja.140.1669807993775; Wed, 30 Nov 2022 03:33:13 -0800 (PST) MIME-Version: 1.0 References: <20221130070158.44221-1-chengkaitao@didiglobal.com> In-Reply-To: From: Tao pilgrim Date: Wed, 30 Nov 2022 19:33:01 +0800 Message-ID: Subject: Re: [PATCH] mm: memcontrol: protect the memory in cgroup from being oom killed To: Bagas Sanjaya Cc: 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, 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 , chengkaitao@didiglobal.com Content-Type: text/plain; charset="UTF-8" ARC-Authentication-Results: i=1; imf18.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=cgrBYVcG; spf=pass (imf18.hostedemail.com: domain of pilgrimtao@gmail.com designates 209.85.208.175 as permitted sender) smtp.mailfrom=pilgrimtao@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1669807995; a=rsa-sha256; cv=none; b=rvevbC40uTAB+zn/BlGStu22SWwRlK/6aL4YOt5ixJCE2SWJLv3XlSGcsuMtg+lYv1J9Oa 8Rr90fXCBEHVjuIJJtMuadVy7yMVCQ1qrc2GuTvHqpTaVEpZ2XMuB47shIWJIJJgp5bAq2 Jzxlx+6xptv/rqSZiQMTmlKrND7NgIc= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1669807995; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=bbgF/8QJth7Q6iZLlIiOpcOOnk+o4nClIAC+d8Lf9z0=; b=ocbX6d9PUjclNj3OPuycHVlvPeu+F12DKX1pnWSdeQiQegIAg27Ikf5KhFTOGkZHLTcdZK tagkRGjzq7JUPnOpR0Y6x0HgnYHDfwVPbS12+xppYjrLU7IQ99sgzE7pTucjjqG8ffN+vG MqaALWbxJu4BYsSwJJANh5RQwNc5yuA= Authentication-Results: imf18.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=cgrBYVcG; spf=pass (imf18.hostedemail.com: domain of pilgrimtao@gmail.com designates 209.85.208.175 as permitted sender) smtp.mailfrom=pilgrimtao@gmail.com; dmarc=pass (policy=none) header.from=gmail.com X-Rspamd-Server: rspam01 X-Stat-Signature: ecb5i3ga7sgnbrhxse4x6q474o7msjkn X-Rspamd-Queue-Id: 878591C000E X-Rspam-User: X-HE-Tag: 1669807995-813901 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, Nov 30, 2022 at 4:41 PM Bagas Sanjaya wrote: > > On 11/30/22 14:01, chengkaitao wrote: > > From: chengkaitao > > > > 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. Hi Bagas Sanjaya, I'm not an employee of ZTE, just an ordinary developer. I really don't know all the details about community and ZTE, The reason why I cc cgel.zte@gmail.com is because the output of the script has the address . If there is any error in the format of the email, I will try my best to correct it. > > 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 > -- Yours, Kaitao Cheng