From: Mina Almasry <almasrymina@google.com>
Cc: Mina Almasry <almasrymina@google.com>,
Michal Hocko <mhocko@suse.com>, "Theodore Ts'o" <tytso@mit.edu>,
Greg Thelen <gthelen@google.com>,
Shakeel Butt <shakeelb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Roman Gushchin <songmuchun@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
riel@surriel.com, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, cgroups@vger.kernel.org
Subject: [PATCH v1 3/5] mm/oom: handle remote ooms
Date: Mon, 8 Nov 2021 13:19:57 -0800 [thread overview]
Message-ID: <20211108211959.1750915-4-almasrymina@google.com> (raw)
In-Reply-To: <20211108211959.1750915-1-almasrymina@google.com>
On remote ooms (OOMs due to remote charging), the oom-killer will attempt
to find a task to kill in the memcg under oom, if the oom-killer
is unable to find one, the oom-killer should simply return ENOMEM to the
allocating process.
If we're in pagefault path and we're unable to return ENOMEM to the
allocating process, we instead kill the allocating process.
Signed-off-by: Mina Almasry <almasrymina@google.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Theodore Ts'o <tytso@mit.edu>
Cc: Greg Thelen <gthelen@google.com>
Cc: Shakeel Butt <shakeelb@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>
Cc: Roman Gushchin <songmuchun@bytedance.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Hugh Dickins <hughd@google.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: Muchun Song <songmuchun@bytedance.com>
Cc: riel@surriel.com
Cc: linux-mm@kvack.org
Cc: linux-fsdevel@vger.kernel.org
Cc: cgroups@vger.kernel.org
---
mm/memcontrol.c | 21 +++++++++++++++++++++
mm/oom_kill.c | 21 +++++++++++++++++++++
2 files changed, 42 insertions(+)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 2e4c20d09f959..fc9c6280266b6 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -2664,6 +2664,27 @@ int mem_cgroup_get_name_from_sb(struct super_block *sb, char *buf, size_t len)
return ret < 0 ? ret : 0;
}
+/*
+ * Returns true if current's mm is a descendant of the memcg_under_oom (or
+ * equal to it). False otherwise. This is used by the oom-killer to detect
+ * ooms due to remote charging.
+ */
+bool is_remote_oom(struct mem_cgroup *memcg_under_oom)
+{
+ struct mem_cgroup *current_memcg;
+ bool is_remote_oom;
+
+ if (!memcg_under_oom)
+ return false;
+
+ current_memcg = get_mem_cgroup_from_mm(current->mm);
+ is_remote_oom =
+ !mem_cgroup_is_descendant(current_memcg, memcg_under_oom);
+ css_put(¤t_memcg->css);
+
+ return is_remote_oom;
+}
+
/*
* Set or clear (if @memcg is NULL) charge association from file system to
* memcg. If @memcg != NULL, then a css reference must be held by the caller to
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 0a7e16b16b8c3..556329dee273f 100644
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -1106,6 +1106,27 @@ bool out_of_memory(struct oom_control *oc)
}
select_bad_process(oc);
+
+ /*
+ * For remote ooms in userfaults, we have no choice but to kill the
+ * allocating process.
+ */
+ if (!oc->chosen && is_remote_oom(oc->memcg) && current->in_user_fault &&
+ !oom_unkillable_task(current)) {
+ get_task_struct(current);
+ oc->chosen = current;
+ oom_kill_process(
+ oc, "Out of memory (Killing remote allocating task)");
+ return true;
+ }
+
+ /*
+ * For remote ooms in non-userfaults, simply return ENOMEM to the
+ * caller.
+ */
+ if (!oc->chosen && is_remote_oom(oc->memcg))
+ return false;
+
/* Found nothing?!?! */
if (!oc->chosen) {
dump_header(oc, NULL);
--
2.34.0.rc0.344.g81b53c2807-goog
next prev parent reply other threads:[~2021-11-08 21:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211108211959.1750915-1-almasrymina@google.com>
2021-11-08 21:19 ` [PATCH v1 1/5] mm/shmem: support deterministic charging of tmpfs Mina Almasry
2021-11-08 22:10 ` Dave Chinner
2021-11-08 23:41 ` Matthew Wilcox
2021-11-09 1:18 ` Dave Chinner
2021-11-09 23:56 ` Mina Almasry
2021-11-10 1:15 ` Mina Almasry
2021-11-15 17:53 ` Shakeel Butt
2021-11-09 1:15 ` Roman Gushchin
2021-11-08 21:19 ` [PATCH v1 2/5] mm: add tmpfs memcg= permissions check Mina Almasry
2021-11-08 21:19 ` Mina Almasry [this message]
2021-11-09 1:19 ` [PATCH v1 3/5] mm/oom: handle remote ooms Roman Gushchin
2021-11-08 21:19 ` [PATCH v1 4/5] mm, shmem: add tmpfs memcg= option documentation Mina Almasry
2021-11-08 21:19 ` [PATCH v1 5/5] mm, shmem, selftests: add tmpfs memcg= mount option tests 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=20211108211959.1750915-4-almasrymina@google.com \
--to=almasrymina@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=riel@surriel.com \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=tj@kernel.org \
--cc=tytso@mit.edu \
--cc=vdavydov.dev@gmail.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