Commit 9b8b1754 authored by Jakub Kicinski's avatar Jakub Kicinski Committed by Linus Torvalds
Browse files

mm, memcg: do not high throttle allocators based on wraparound

If a cgroup violates its memory.high constraints, we may end up unduly
penalising it.  For example, for the following hierarchy:

  A:   max high, 20 usage
  A/B: 9 high, 10 usage
  A/C: max high, 10 usage

We would end up doing the following calculation below when calculating
high delay for A/B:

  A/B: 10 - 9 = 1...
  A:   20 - PAGE_COUNTER_MAX = 21, so set max_overage to 21.

This gets worse with higher disparities in usage in the parent.

I have no idea how this disappeared from the final version of the patch,
but it is certainly Not Good(tm).  This wasn't obvious in testing because,
for a simple cgroup hierarchy with only one child, the result is usually
roughly the same.  It's only in more complex hierarchies that things go
really awry (although still, the effects are limited to a maximum of 2
seconds in schedule_timeout_killable at a maximum).

[ changelog]
Fixes: e26733e0

 ("mm, memcg: throttle allocators based on ancestral memory.high")
Signed-off-by: default avatarJakub Kicinski <>
Signed-off-by: default avatarChris Down <>
Signed-off-by: default avatarAndrew Morton <>
Acked-by: default avatarMichal Hocko <>
Cc: Johannes Weiner <>
Cc: <>	[5.4.x]

Signed-off-by: default avatarLinus Torvalds <>
parent 25efb2ff
......@@ -2336,6 +2336,9 @@ static unsigned long calculate_high_delay(struct mem_cgroup *memcg,
usage = page_counter_read(&memcg->memory);
high = READ_ONCE(memcg->high);
if (usage <= high)
* Prevent division by 0 in overage calculation by acting as if
* it was a threshold of 1 page
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment