mm: memcg: stop reclaim when a limit update is superseded
Subsystems (3)
PATCH 1/1 mm: memcg: stop reclaim when a limit update is superseded
From: Guopeng Zhang <[email protected]>
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
Check the current limit at the start of each reclaim iteration and stop if it no longer matches the writer's target.
---
Reproducer:
Populate a cgroup with anonymous memory and disable swapping. Lower memory.max from one open file, then restore it to "max" through another open file after the new limit becomes visible.
Without the patch, the first writer remains blocked and repeatedly increments the OOM event counter. With the patch, it returns normally.
mm/memcontrol.c | 6 ++++++ 1 file changed, 6 insertions(+)
mm/memcontrol.c +6 -0
@@ -4798,6 +4798,9 @@ static ssize_t memory_high_write(struct kernfs_open_file *of,unsigned long nr_pages =page_counter_read (&memcg->memory);unsigned long reclaimed; +if (high !=READ_ONCE (memcg->memory.high)) +break ; +if (nr_pages <= high)break ;
@@ -4853,6 +4856,9 @@ static ssize_t memory_max_write(struct kernfs_open_file *of,for (;;) {unsigned long nr_pages =page_counter_read (&memcg->memory); +if (max !=READ_ONCE (memcg->memory.max)) +break ; +if (nr_pages <= max)break ;
Signature · 1 line
2.25.1
Quoted 9 lines · Guopeng Zhang
From: Guopeng Zhang <[email protected]>
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
Quoted 9 lines
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
Check the current limit at the start of each reclaim iteration and stop if it no longer matches the writer's target.
Fix looks correct to me.
Nit: the message lumps both paths together, but only memory.max loops indefinitely. memory.high has no OOM path, so it just spins MAX_RECLAIM_RETRIES times and breaks on its own. Worth a line to avoid conflating the severity.
Quoted 40 lines
Fixes 8c8c383c04f6 ("mm: memcontrol: try harder to set a new memory.high")Fixes b6e6edcfa405 ("mm: memcontrol: reclaim and OOM kill when shrinking memory.max below usage")Signed-off-by Guopeng Zhang <[email protected]>---
Reproducer:Populate a cgroup with anonymous memory and disable swapping. Lower memory.max from one open file, then restore it to "max" through another open file after the new limit becomes visible.
Without the patch, the first writer remains blocked and repeatedly increments the OOM event counter. With the patch, it returns normally.
mm/memcontrol.c | 6 ++++++ 1 file changed, 6 insertions(+)mm/memcontrol.c +6
-0@@ -4798,6 +4798,9 @@ static ssize_t memory_high_write(struct kernfs_open_file *of,unsigned long nr_pages =page_counter_read (&memcg->memory);unsigned long reclaimed; +if (high !=READ_ONCE (memcg->memory.high)) +break ; +if (nr_pages <= high)break ;@@ -4853,6 +4856,9 @@ static ssize_t memory_max_write(struct kernfs_open_file *of,for (;;) {unsigned long nr_pages =page_counter_read (&memcg->memory); +if (max !=READ_ONCE (memcg->memory.max)) +break ; +if (nr_pages <= max)break ;
Quoted 22 lines · Tao Cui
Quoted 9 lines · Guopeng Zhang
From: Guopeng Zhang <[email protected]>
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
Quoted 9 lines
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
Check the current limit at the start of each reclaim iteration and stop if it no longer matches the writer's target.
Quoted 9 lines
Fix looks correct to me.
Acked-by Tao Cui <[email protected]>Nit: the message lumps both paths together, but only memory.max loops indefinitely. memory.high has no OOM path, so it just spins
MAX_RECLAIM_RETRIEStimes and breaks on its own. Worth a line to avoid conflating the severity.
Hi,
Thanks for the review and Ack.
The message separates the two cases: the first paragraph describes the stale-target reclaim behavior common to both, while the "For memory.max" paragraph describes the OOM-based indefinite loop.
One detail is that memory.high is not limited to MAX_RECLAIM_RETRIES iterations. The retry counter is decremented only when reclaim makes no progress:
if (!reclaimed && !nr_retries--)
break;If reclaim continues to make progress while pages are refaulted, nr_retries is not decremented and the loop can still fail to converge.
Thanks,
Guopeng
Quoted 41 lines
Quoted 40 lines
Fixes 8c8c383c04f6 ("mm: memcontrol: try harder to set a new memory.high")Fixes b6e6edcfa405 ("mm: memcontrol: reclaim and OOM kill when shrinking memory.max below usage")Signed-off-by Guopeng Zhang <[email protected]>---
Reproducer:Populate a cgroup with anonymous memory and disable swapping. Lower memory.max from one open file, then restore it to "max" through another open file after the new limit becomes visible.
Without the patch, the first writer remains blocked and repeatedly increments the OOM event counter. With the patch, it returns normally.
mm/memcontrol.c | 6 ++++++ 1 file changed, 6 insertions(+)mm/memcontrol.c +6
-0@@ -4798,6 +4798,9 @@ static ssize_t memory_high_write(struct kernfs_open_file *of,unsigned long nr_pages =page_counter_read (&memcg->memory);unsigned long reclaimed; +if (high !=READ_ONCE (memcg->memory.high)) +break ; +if (nr_pages <= high)break ;@@ -4853,6 +4856,9 @@ static ssize_t memory_max_write(struct kernfs_open_file *of,for (;;) {unsigned long nr_pages =page_counter_read (&memcg->memory); +if (max !=READ_ONCE (memcg->memory.max)) +break ; +if (nr_pages <= max)break ;
Andrew Morton
maintainerQuoted 9 lines · On Fri, 24 Jul 2026 10:18:05 +0800 Guopeng Zhang <[email protected]>…
From: Guopeng Zhang <[email protected]>
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
Quoted 8 lines
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
Check the current limit at the start of each reclaim iteration and stop if it no longer matches the writer's target.
Thanks.
Quoted 1 line
Fixes 8c8c383c04f6 ("mm: memcontrol: try harder to set a new memory.high")
Dec 2019
Quoted 1 line
Fixes b6e6edcfa405 ("mm: memcontrol: reclaim and OOM kill when shrinking memory.max below usage")
Mar 2016
Having two Fixes: targets is confusing. The Fixes: identifies which kernel versions should be patched, so how is anyone to figure out whether their 2018 kernel actually needs the patch?
I assume one of the two hunks is for 2019 and the other is for 2016, so two separate patches each with a single Fixes: would be more useful.
That being said, both versions are so ancient that it probably doesn't matter. In fact the bug seems so obscure that I'm not planning on adding cc:stable to this anyway. Maintainers, please advise.
Quoted 8 lines
Reproducer:
Populate a cgroup with anonymous memory and disable swapping. Lower memory.max from one open file, then restore it to "max" through another open file after the new limit becomes visible.
Without the patch, the first writer remains blocked and repeatedly increments the OOM event counter. With the patch, it returns normally.
This is nice info - I'll promote it into the permanent changelog.
I'll queue the patch for 7.3-rc1 and shall await maintainer input, please.
Quoted 28 lines · Andrew Morton
Quoted 9 lines · On Fri, 24 Jul 2026 10:18:05 +0800 Guopeng Zhang <[email protected]>…
From: Guopeng Zhang <[email protected]>
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
Quoted 8 lines
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
Check the current limit at the start of each reclaim iteration and stop if it no longer matches the writer's target.
Thanks.
Quoted 1 line
Fixes 8c8c383c04f6 ("mm: memcontrol: try harder to set a new memory.high")Dec 2019
Quoted 1 line
Fixes b6e6edcfa405 ("mm: memcontrol: reclaim and OOM kill when shrinking memory.max below usage")
Quoted 9 lines
Mar 2016
Having two Fixes: targets is confusing. The Fixes: identifies which kernel versions should be patched, so how is anyone to figure out whether their 2018 kernel actually needs the patch?
I assume one of the two hunks is for 2019 and the other is for 2016, so two separate patches each with a single Fixes: would be more useful.
Thanks, that makes sense.
For similar cases where separate code paths were introduced by different commits and have different affected-version ranges, I will split the fixes into separate patches, each with its own Fixes tag.
Quoted 19 lines
That being said, both versions are so ancient that it probably doesn't matter. In fact the bug seems so obscure that I'm not planning on adding cc:stable to this anyway. Maintainers, please advise.
Quoted 8 lines
Reproducer:
Populate a cgroup with anonymous memory and disable swapping. Lower memory.max from one open file, then restore it to "max" through another open file after the new limit becomes visible.
Without the patch, the first writer remains blocked and repeatedly increments the OOM event counter. With the patch, it returns normally.
This is nice info - I'll promote it into the permanent changelog.
I'll queue the patch for 7.3-rc1 and shall await maintainer input, please.
Quoted 9 lines · Guopeng Zhang
From: Guopeng Zhang <[email protected]>
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
Quoted 5 lines
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
The current behavior is deliberate as described in b6e6edcfa4056. What is an actual problem you are trying to fix?
Signature · 2 lines
Michal Hocko SUSE Labs
Quoted 10 lines · Michal Hocko
Quoted 9 lines · Guopeng Zhang
From: Guopeng Zhang <[email protected]>
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
Quoted 8 lines
Quoted 5 lines
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
The current behavior is deliberate as described in
b6e6edcfa4056. What is an actual problem you are trying to fix?
Thanks for raising this. I agree that the behavior introduced by b6e6edcfa405 is deliberate while the limit installed by the writer remains current. The problem occurs when that limit is overwritten by a later write through another open file.
Writer A stores a low memory.max and enters synchronous reclaim. Writer B then restores memory.max to "max". A still compares usage against its local old target, while mem_cgroup_out_of_memory() checks the current memory.max. Since 1378b37d03e8, the current-margin check in mem_cgroup_out_of_memory() sees sufficient margin and returns true without selecting a victim. Once the reclaim retries are exhausted, A therefore loops indefinitely and increments the oom counter in memory.events on every iteration.
I reproduced this with a cgroup holding 128 MiB of anonymous memory and with swapping disabled for the cgroup. Writer A lowered memory.max to 32 MiB. After that value became visible, writer B restored memory.max to "max" through another open file.
On the unpatched kernel, A remained blocked after B's write, and the oom counter in memory.events increased from 37333 to 13512861 during the reproducer's one-second sampling interval. With the patch, the same reproducer observed A return after B superseded A's limit.
The new check does not change the behavior introduced by b6e6edcfa405 while the writer's target remains the active limit. For the indefinite loop described above, 1378b37d03e8 appears to be the more precise
Fixes: target for the memory.max hunk. Does that match your reading of the history?
Thanks,
Guopeng
Quoted 36 lines · Guopeng Zhang
Quoted 10 lines · Michal Hocko
Quoted 9 lines · Guopeng Zhang
From: Guopeng Zhang <[email protected]>
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
Quoted 8 lines
Quoted 5 lines
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
The current behavior is deliberate as described in
b6e6edcfa4056. What is an actual problem you are trying to fix?Thanks for raising this. I agree that the behavior introduced by
b6e6edcfa405is deliberate while the limit installed by the writer remains current. The problem occurs when that limit is overwritten by a later write through another open file.Writer A stores a low memory.max and enters synchronous reclaim. Writer B then restores memory.max to "max". A still compares usage against its local old target, while
mem_cgroup_out_of_memory()checks the current memory.max. Since1378b37d03e8, the current-margin check inmem_cgroup_out_of_memory()sees sufficient margin and returns true without selecting a victim. Once the reclaim retries are exhausted, A therefore loops indefinitely and increments the oom counter in memory.events on every iteration.
Quoted 4 lines
I reproduced this with a cgroup holding 128 MiB of anonymous memory and with swapping disabled for the cgroup. Writer A lowered memory.max to 32 MiB. After that value became visible, writer B restored memory.max to "max" through another open file.
Is this trying to replicate any real workload? One would expect that writers to limit do some sort of coordination otherwise the exact behavior is not really well defined.
Quoted 10 lines
On the unpatched kernel, A remained blocked after B's write, and the oom counter in memory.events increased from 37333 to 13512861 during the reproducer's one-second sampling interval. With the patch, the same reproducer observed A return after B superseded A's limit.
The new check does not change the behavior introduced by
b6e6edcfa405while the writer's target remains the active limit. For the indefinite loop described above,1378b37d03e8appears to be the more precise
Fixes: target for the memory.max hunk. Does that match your reading of the history?
Well, to be really honest I am not really convinced this needs fixing. And if yes, your patch changes a well established behavior existing userspace might already depend on. While your described case doesn't look great it doesn't seem really harmful and the looping task is killable.
Signature · 2 lines
Michal Hocko SUSE Labs
Quoted 37 lines · Michal Hocko
Quoted 36 lines · Guopeng Zhang
Quoted 10 lines · Michal Hocko
Quoted 9 lines · Guopeng Zhang
From: Guopeng Zhang <[email protected]>
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
Quoted 8 lines
Quoted 5 lines
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
The current behavior is deliberate as described in
b6e6edcfa4056. What is an actual problem you are trying to fix?Thanks for raising this. I agree that the behavior introduced by
b6e6edcfa405is deliberate while the limit installed by the writer remains current. The problem occurs when that limit is overwritten by a later write through another open file.Writer A stores a low memory.max and enters synchronous reclaim. Writer B then restores memory.max to "max". A still compares usage against its local old target, while
mem_cgroup_out_of_memory()checks the current memory.max. Since1378b37d03e8, the current-margin check inmem_cgroup_out_of_memory()sees sufficient margin and returns true without selecting a victim. Once the reclaim retries are exhausted, A therefore loops indefinitely and increments the oom counter in memory.events on every iteration.
Quoted 9 lines
Quoted 4 lines
I reproduced this with a cgroup holding 128 MiB of anonymous memory and with swapping disabled for the cgroup. Writer A lowered memory.max to 32 MiB. After that value became visible, writer B restored memory.max to "max" through another open file.
Is this trying to replicate any real workload? One would expect that writers to limit do some sort of coordination otherwise the exact behavior is not really well defined.
No, this was not motivated by a reported production workload. We found it through automated randomized testing for our cgroup observability work and reduced it to the reproducer above.
Quoted 11 lines
Quoted 10 lines
On the unpatched kernel, A remained blocked after B's write, and the oom counter in memory.events increased from 37333 to 13512861 during the reproducer's one-second sampling interval. With the patch, the same reproducer observed A return after B superseded A's limit.
The new check does not change the behavior introduced by
b6e6edcfa405while the writer's target remains the active limit. For the indefinite loop described above,1378b37d03e8appears to be the more precise
Fixes: target for the memory.max hunk. Does that match your reading of the history?
Quoted 5 lines
Well, to be really honest I am not really convinced this needs fixing. And if yes, your patch changes a well established behavior existing userspace might already depend on. While your described case doesn't look great it doesn't seem really harmful and the looping task is killable.
That makes sense. Without a concrete workload showing practical impact, there is not enough justification to change the established behavior. We can revisit this if such a workload turns up.
Andrew, please drop this patch from your queue.
Thanks,
Guopeng
Quoted 8 lines · Guopeng Zhang
Quoted 5 lines · Michal Hocko
Quoted 4 lines · Guopeng Zhang
Quoted 1 line · Michal Hocko
On Fri 24-07-26 10:18:05, Guopeng Zhang wrote:
[...]
Quoted 8 lines
Quoted 4 lines
Is this trying to replicate any real workload? One would expect that writers to limit do some sort of coordination otherwise the exact behavior is not really well defined.
No, this was not motivated by a reported production workload. We found it through automated randomized testing for our cgroup observability work and reduced it to the reproducer above.
This is an important detail to be mentioned in the changelog. Describing motivation for a change is really important, especially if it has direct impact in user interface behavior.
Signature · 2 lines
Michal Hocko SUSE Labs
Quoted 5 lines · On Wed, 29 Jul 2026 10:02:22 +0200 Michal Hocko <[email protected]> wrote:
Quoted 5 lines
Quoted 4 lines
Is this trying to replicate any real workload? One would expect that writers to limit do some sort of coordination otherwise the exact behavior is not really well defined.
Quoted 7 lines
Quoted 3 lines
No, this was not motivated by a reported production workload. We found it through automated randomized testing for our cgroup observability work and reduced it to the reproducer above.
This is an important detail to be mentioned in the changelog. Describing motivation for a change is really important, especially if it has direct impact in user interface behavior.
I've been adding details to the changelog as they are revealed to us. Below is the state of play.
I await maintainer guidance on how to proceed with this!
The worst-case effects look pretty bad actually. Should I add cc:stable?
From: Guopeng Zhang <[email protected]>
Subject: mm: memcg: stop reclaim when a limit update is superseded
Date: Fri, 24 Jul 2026 10:18:05 +0800
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
Check the current limit at the start of each reclaim iteration and stop if it no longer matches the writer's target.
Reproducer:
Populate a cgroup with anonymous memory and disable swapping. Lower memory.max from one open file, then restore it to "max" through another open file after the new limit becomes visible.
Without the patch, the first writer remains blocked and repeatedly increments the OOM event counter. With the patch, it returns normally.
This was not motivated by a reported production workload. We found it through automated randomized testing for our cgroup observability work and reduced it to the reproducer above.
---
mm/memcontrol.c | 6 ++++++ 1 file changed, 6 insertions(+)
mm/memcontrol.c renamed from mm/memcontrol.c~mm-memcg-stop-reclaim-when-a-limit-update-is-superseded +6 -0
@@ -4837,6 +4837,9 @@ static ssize_t memory_high_write(structunsigned long nr_pages =page_counter_read (&memcg->memory);unsigned long reclaimed; +if (high !=READ_ONCE (memcg->memory.high)) +break ; +if (nr_pages <= high)break ;
@@ -4892,6 +4895,9 @@ static ssize_t memory_max_write(struct kfor (;;) {unsigned long nr_pages =page_counter_read (&memcg->memory); +if (max !=READ_ONCE (memcg->memory.max)) +break ; +if (nr_pages <= max)break ;
_
Quoted 55 lines · Andrew Morton
Quoted 5 lines · On Wed, 29 Jul 2026 10:02:22 +0200 Michal Hocko <[email protected]> wrote:
Quoted 5 lines
Quoted 4 lines
Is this trying to replicate any real workload? One would expect that writers to limit do some sort of coordination otherwise the exact behavior is not really well defined.
Quoted 7 lines
Quoted 3 lines
No, this was not motivated by a reported production workload. We found it through automated randomized testing for our cgroup observability work and reduced it to the reproducer above.
This is an important detail to be mentioned in the changelog. Describing motivation for a change is really important, especially if it has direct impact in user interface behavior.
I've been adding details to the changelog as they are revealed to us. Below is the state of play.
I await maintainer guidance on how to proceed with this!
The worst-case effects look pretty bad actually. Should I add cc:stable?
From: Guopeng Zhang <[email protected]>
Subject: mm: memcg: stop reclaim when a limit update is superseded
Date: Fri, 24 Jul 2026 10:18:05 +0800kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted. The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
Check the current limit at the start of each reclaim iteration and stop if it no longer matches the writer's target.
Reproducer:
Populate a cgroup with anonymous memory and disable swapping. Lower memory.max from one open file, then restore it to "max" through another open file after the new limit becomes visible.
Without the patch, the first writer remains blocked and repeatedly increments the OOM event counter. With the patch, it returns normally.
This was not motivated by a reported production workload. We found it through automated randomized testing for our cgroup observability work and reduced it to the reproducer above.
Quoted 11 lines
Fixes 8c8c383c04f6 ("mm: memcontrol: try harder to set a new memory.high")Fixes b6e6edcfa405 ("mm: memcontrol: reclaim and OOM kill when shrinking memory.max below usage")Signed-off-by Guopeng Zhang <[email protected]>Acked-by Tao Cui <[email protected]>Cc Johannes Weiner <[email protected]>Cc Michal Hocko <[email protected]>Cc Muchun Song <[email protected]>Cc Roman Gushchin <[email protected]>Cc Shakeel Butt <[email protected]>Signed-off-by Andrew Morton <[email protected]>
This looks good to me. If the culprits had been more recent, it might have made sense to split this in two, one for each Fixes. But it's 4.6 and 5.5, so I'd assume any still alive backport target would want them both at this point anyway.
Quoted 15 lines · Michal Hocko
Quoted 8 lines · Guopeng Zhang
Quoted 5 lines · Michal Hocko
Quoted 4 lines · Guopeng Zhang
Quoted 1 line · Michal Hocko
On Fri 24-07-26 10:18:05, Guopeng Zhang wrote:
[...]
Quoted 5 lines
Quoted 4 lines
Is this trying to replicate any real workload? One would expect that writers to limit do some sort of coordination otherwise the exact behavior is not really well defined.
Quoted 7 lines
Quoted 3 lines
No, this was not motivated by a reported production workload. We found it through automated randomized testing for our cgroup observability work and reduced it to the reproducer above.
This is an important detail to be mentioned in the changelog. Describing motivation for a change is really important, especially if it has direct impact in user interface behavior.
Thanks for the guidance. I will take the feedback from this patch into account when preparing similar changes in the future.