From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, kareemem@amazon.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y] memcg: fix soft lockup in the OOM process
Date: Fri, 14 Mar 2025 19:10:25 -0400 [thread overview]
Message-ID: <20250314081509-114460a8b7f811a9@stable.kernel.org> (raw)
In-Reply-To: <20250313180309.41770-1-kareemem@amazon.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
❌ Build failures detected
The upstream commit SHA1 provided is correct: ade81479c7dda1ce3eedb215c78bc615bbd04f06
WARNING: Author mismatch between patch and upstream commit:
Backport author: Abdelkareem Abdelsaamad<kareemem@amazon.com>
Commit author: Chen Ridong<chenridong@huawei.com>
Status in newer kernel trees:
6.13.y | Present (different SHA1: 465768342918)
6.12.y | Present (different SHA1: c3a3741db8c1)
6.6.y | Present (different SHA1: 972486d37169)
6.1.y | Present (different SHA1: 0a09d56e1682)
5.15.y | Present (different SHA1: a9042dbc1ed4)
Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly.
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y | Failed | N/A |
Build Errors:
Patch failed to apply on stable/linux-5.10.y. Reject:
diff a/mm/memcontrol.c b/mm/memcontrol.c (rejected hunks)
@@ -1312,6 +1312,7 @@ int mem_cgroup_scan_tasks(struct mem_cgroup *memcg,
{
struct mem_cgroup *iter;
int ret = 0;
+ int i = 0;
BUG_ON(memcg == root_mem_cgroup);
@@ -1320,8 +1321,12 @@ int mem_cgroup_scan_tasks(struct mem_cgroup *memcg,
struct task_struct *task;
css_task_iter_start(&iter->css, CSS_TASK_ITER_PROCS, &it);
- while (!ret && (task = css_task_iter_next(&it)))
+ while (!ret && (task = css_task_iter_next(&it))) {
+ /* Avoid potential softlockup warning */
+ if ((++i & 1023) == 0)
+ cond_resched();
ret = fn(task, arg);
+ }
css_task_iter_end(&it);
if (ret) {
mem_cgroup_iter_break(memcg, iter);
diff a/mm/oom_kill.c b/mm/oom_kill.c (rejected hunks)
@@ -43,6 +43,7 @@
#include <linux/kthread.h>
#include <linux/init.h>
#include <linux/mmu_notifier.h>
+#include <linux/nmi.h>
#include <asm/tlb.h>
#include "internal.h"
@@ -430,10 +431,15 @@ static void dump_tasks(struct oom_control *oc)
mem_cgroup_scan_tasks(oc->memcg, dump_task, oc);
else {
struct task_struct *p;
+ int i = 0;
rcu_read_lock();
- for_each_process(p)
+ for_each_process(p) {
+ /* Avoid potential softlockup warning */
+ if ((++i & 1023) == 0)
+ touch_softlockup_watchdog();
dump_task(p, oc);
+ }
rcu_read_unlock();
}
}
next prev parent reply other threads:[~2025-03-14 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 18:03 [PATCH 5.10.y] memcg: fix soft lockup in the OOM process Abdelkareem Abdelsaamad
2025-03-14 23:10 ` Sasha Levin [this message]
2025-03-16 6:18 ` Greg KH
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=20250314081509-114460a8b7f811a9@stable.kernel.org \
--to=sashal@kernel.org \
--cc=kareemem@amazon.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.