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 X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DBFB0C433E0 for ; Mon, 13 Jul 2020 23:51:11 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 62AFB2089D for ; Mon, 13 Jul 2020 23:51:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 62AFB2089D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=i-love.sakura.ne.jp Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id AEA1B8D0002; Mon, 13 Jul 2020 19:51:10 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id A9AAE8D0001; Mon, 13 Jul 2020 19:51:10 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 9B2078D0002; Mon, 13 Jul 2020 19:51:10 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0156.hostedemail.com [216.40.44.156]) by kanga.kvack.org (Postfix) with ESMTP id 867D78D0001 for ; Mon, 13 Jul 2020 19:51:10 -0400 (EDT) Received: from smtpin24.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 214921EFD for ; Mon, 13 Jul 2020 23:51:10 +0000 (UTC) X-FDA: 77034701100.24.sort19_110b08e26eec Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin24.hostedemail.com (Postfix) with ESMTP id EF7C01A4A7 for ; Mon, 13 Jul 2020 23:51:09 +0000 (UTC) X-HE-Tag: sort19_110b08e26eec X-Filterd-Recvd-Size: 2258 Received: from www262.sakura.ne.jp (www262.sakura.ne.jp [202.181.97.72]) by imf14.hostedemail.com (Postfix) with ESMTP for ; Mon, 13 Jul 2020 23:51:08 +0000 (UTC) Received: from fsav103.sakura.ne.jp (fsav103.sakura.ne.jp [27.133.134.230]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id 06DNovLa025198; Tue, 14 Jul 2020 08:50:57 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav103.sakura.ne.jp (F-Secure/fsigk_smtp/550/fsav103.sakura.ne.jp); Tue, 14 Jul 2020 08:50:57 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/550/fsav103.sakura.ne.jp) Received: from [192.168.1.9] (M106072142033.v4.enabler.ne.jp [106.72.142.33]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id 06DNoubV025194 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jul 2020 08:50:57 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Subject: Re: [PATCH] mm, oom: don't invoke oom killer if current has been reapered To: Yafang Shao Cc: mhocko@kernel.org, rientjes@google.com, akpm@linux-foundation.org, linux-mm@kvack.org References: <1594437481-11144-1-git-send-email-laoar.shao@gmail.com> From: Tetsuo Handa Message-ID: <06806cf0-a122-e002-191f-348298358882@i-love.sakura.ne.jp> Date: Tue, 14 Jul 2020 08:50:57 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <1594437481-11144-1-git-send-email-laoar.shao@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: EF7C01A4A7 X-Spamd-Result: default: False [0.00 / 100.00] X-Rspamd-Server: rspam03 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 2020/07/11 12:18, Yafang Shao wrote: > If the current's MMF_OOM_SKIP is set, it means that the current is exiting > or dying and likely to realease its address space. So we don't need to > invoke the oom killer again. Otherwise that may cause some unexpected > issues, for example, bellow is the issue found in our production > environment. What kernel version are you using? Commit 7775face207922ea ("memcg: killed threads should not invoke memcg OOM killer") should solve this problem.