A task already in exit can get stuck trying to allocate pages, if its
cgroup is at the memory.max limit, the cgroup is using zswap, but
zswap writeback is enabled, and the remaining memory in the cgroup is
not compressible.
This seems like an unlikely confluence of events, but it can happen
quite easily if a cgroup is OOM killed due to exceeding its memory.max
limit, and all the tasks in the cgroup are trying to exit simultaneously.
When this happens, it can sometimes take hours for tasks to exit,
as they are all trying to squeeze things into zswap to bring the group's
memory consumption below memory.max.
Allowing these exiting programs to push some memory from their own
cgroup into swap allows them to quickly bring the cgroup's memory
consumption below memory.max, and exit in seconds rather than hours.
Signed-off-by: Rik van Riel <riel@xxxxxxxxxxx>
---
v2: use mm_match_cgroup as suggested by Yosry Ahmed
mm/memcontrol.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 7b3503d12aaf..ba1cd9c04a02 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -5371,6 +5371,18 @@ bool mem_cgroup_zswap_writeback_enabled(struct mem_cgroup *memcg)
if (!zswap_is_enabled())
return true;
+ /*
+ * Always allow exiting tasks to push data to swap. A process in
+ * the middle of exit cannot get OOM killed, but may need to push
+ * uncompressible data to swap in order to get the cgroup memory
+ * use below the limit, and make progress with the exit.
+ */
+ if (unlikely(current->flags & PF_EXITING)) {
+ struct mm_struct *mm = READ_ONCE(current->mm);
+ if (mm && mm_match_cgroup(mm, memcg))
+ return true;
+ }
+
for (; memcg; memcg = parent_mem_cgroup(memcg))
if (!READ_ONCE(memcg->zswap_writeback))
return false;
--
2.47.0
