Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp1894318ybx; Sat, 2 Nov 2019 08:18:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqzigIsymW1Y+cUKRDte/rCz7pX4tk8umUAifeaARBeLuLMJW16A3NfvODtQDlvvvYcoHQW4 X-Received: by 2002:a17:906:6a06:: with SMTP id o6mr15304331ejr.89.1572707937477; Sat, 02 Nov 2019 08:18:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572707937; cv=none; d=google.com; s=arc-20160816; b=ZdB+yLJKNcp1Rz2K/f6rzbV+JJAF1aMdrRHMX3ZZP2sQVHoi8FQ/6IoqiMqSU94r3n ElYKRgd2MM54bl1a2bUCv1KnyISm2mBuGgmQyhyAXMFhS2H4Qh7zSOr2ZMg4LqIckx/w 4OUpzvZy9/EnIIhgYBSdHZ66L/HQO+JCmQ80xrtXpTiXrUI+E+8YpdijJo4UvaJAGYhw /x2F4Lshrb4jHbuYL72oDrTlB5tcPNo87j3wsfrTbagbtGqT0hLoOyIfyd0eMkKc3y8L tRqm+/lJj1hwTG6NM/ist6EJTlxoEvDPUo677HwT+BYY2ZaBccAdBDKNqQkncelOS6Ox AV8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:message-id:date:cc:to:from:subject:dkim-signature; bh=AR0posdeGGjRMOUjYp9dgJq5OCpwQBAAcmepPzGDKWg=; b=0heHvvqRH2PszeCweXVxAmQp9X5EKDSES7U1iLFEtY7hNXIBD1E13eJAufRoB2mMRu XfMJLDMiC4XraKVqhB4lUraykw5rvKx/lhI6kSMRdDnmbOyJBANPc8NcRHlJ6qP4idfR qfm6rqn2YgJy9cvSv6HVsV/hVhWtwV8g3VH7SXfsYZuZptAIUcyPMSZ3PNgP2qkvmyK3 /BV1EG0TCYmyOpG6MWDZrn7BAUx9IcrT/vCZzpF29vTNuXdYVgpufmH2OnEDvrpUD1Kj bUs7bcqiqOMt23LYJZTClDqfi19djoAhU3kCtPXHGFIwLwveHl+bmx0JdQNqpcqjPX5a qjxQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@yandex-team.ru header.s=default header.b=X9dFktO7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=yandex-team.ru Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q25si8201773ejb.340.2019.11.02.08.18.18; Sat, 02 Nov 2019 08:18:57 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@yandex-team.ru header.s=default header.b=X9dFktO7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=yandex-team.ru Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726958AbfKBPQh (ORCPT + 99 others); Sat, 2 Nov 2019 11:16:37 -0400 Received: from forwardcorp1p.mail.yandex.net ([77.88.29.217]:42376 "EHLO forwardcorp1p.mail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726440AbfKBPQh (ORCPT ); Sat, 2 Nov 2019 11:16:37 -0400 Received: from mxbackcorp1o.mail.yandex.net (mxbackcorp1o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::301]) by forwardcorp1p.mail.yandex.net (Yandex) with ESMTP id 941382E099D; Sat, 2 Nov 2019 18:16:34 +0300 (MSK) Received: from vla1-5826f599457c.qloud-c.yandex.net (vla1-5826f599457c.qloud-c.yandex.net [2a02:6b8:c0d:35a1:0:640:5826:f599]) by mxbackcorp1o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id UjI6F08SWn-GXjiaB0J; Sat, 02 Nov 2019 18:16:34 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1572707794; bh=AR0posdeGGjRMOUjYp9dgJq5OCpwQBAAcmepPzGDKWg=; h=Message-ID:Date:To:From:Subject:Cc; b=X9dFktO77Na/G0mtC2+xSzpD1cMLgWOkM1P9fpb+ypv5Obc9xW91WTB8Mc1xm15fI f+vjegUUhK0i7hnoRfJ+Na/UVVXYuRet+Jx2AzVkMEQdB23FUCLveNYbe34Rajfqob WnSYBjjQfRvF4wy/a3HK7oM0Cf0Nz8wpJRNk4zps= Authentication-Results: mxbackcorp1o.mail.yandex.net; dkim=pass header.i=@yandex-team.ru Received: from dynamic-red.dhcp.yndx.net (dynamic-red.dhcp.yndx.net [2a02:6b8:0:40c:8554:53c0:3d75:2e8a]) by vla1-5826f599457c.qloud-c.yandex.net (nwsmtp/Yandex) with ESMTPSA id kxXcRS1iUB-GXVOVCeE; Sat, 02 Nov 2019 18:16:33 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Subject: [PATCH] mm/memcontrol: update documentation about invoking oom killer From: Konstantin Khlebnikov To: linux-mm@kvack.org, Andrew Morton , linux-kernel@vger.kernel.org Cc: cgroups@vger.kernel.org, Michal Hocko Date: Sat, 02 Nov 2019 18:16:33 +0300 Message-ID: <157270779336.1961.6528158720593572480.stgit@buzz> User-Agent: StGit/0.17.1-dirty MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Since commit 29ef680ae7c2 ("memcg, oom: move out_of_memory back to the charge path") memcg invokes oom killer not only for user page-faults. This means 0-order allocation will either succeed or task get killed. Fixes: 8e675f7af507 ("mm/oom_kill: count global and memory cgroup oom kills") Signed-off-by: Konstantin Khlebnikov --- Documentation/admin-guide/cgroup-v2.rst | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst index 5361ebec3361..eb47815e137b 100644 --- a/Documentation/admin-guide/cgroup-v2.rst +++ b/Documentation/admin-guide/cgroup-v2.rst @@ -1219,8 +1219,13 @@ PAGE_SIZE multiple when read back. Failed allocation in its turn could be returned into userspace as -ENOMEM or silently ignored in cases like - disk readahead. For now OOM in memory cgroup kills - tasks iff shortage has happened inside page fault. + disk readahead. + + Before 4.19 OOM in memory cgroup killed tasks iff + shortage has happened inside page fault, random + syscall may fail with ENOMEM or EFAULT. Since 4.19 + failed memory cgroup allocation invokes oom killer and + keeps retrying until it succeeds. This event is not raised if the OOM killer is not considered as an option, e.g. for failed high-order