From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: "Heyne, Maximilian" <mheyne@amazon.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Sauerwein, David" <dssauerw@amazon.de>,
Sasha Levin <sashal@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 5.15] fs/proc: do_task_stat: use __for_each_thread()
Date: Wed, 9 Jul 2025 17:33:39 +0530 [thread overview]
Message-ID: <ef0e0364-29e2-47c2-8f0a-93f385cebf08@oracle.com> (raw)
In-Reply-To: <20250605-monty-tee-7cec3e1e@mheyne-amazon>
Hi,
+ stable
On 05/06/25 19:37, Heyne, Maximilian wrote:
> From: Oleg Nesterov <oleg@redhat.com>
>
> [ Upstream commit 7904e53ed5a20fc678c01d5d1b07ec486425bb6a ]
>
> do/while_each_thread should be avoided when possible.
>
> Link: https://lkml.kernel.org/r/20230909164501.GA11581@redhat.com
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> Cc: Eric W. Biederman <ebiederm@xmission.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Stable-dep-of: 7601df8031fd ("fs/proc: do_task_stat: use sig->stats_lock to=ather the threads/children stats")
> [mheyne: adjusted context]
> Signed-off-by: Maximilian Heyne <mheyne@amazon.de>
> ---
>
> Compile-tested only.
> We're seeing soft lock-ups with 5.10.237 because of the backport of
> commit 4fe85bdaabd6 ("fs/proc: do_task_stat: use sig->stats_lock to
> gather the threads/children stats"). I'm assuming this is broken on 5.15
> too.
>
Note: We saw this as well after backporting the above mentioned commit
from 5.15.y and your backport resolves it for us as well on 5.15.y based
branch.
Thanks,
Harshit
> ---
> fs/proc/array.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/proc/array.c b/fs/proc/array.c
> index 2cb01aaa67187..2ff568dc58387 100644
> --- a/fs/proc/array.c
> +++ b/fs/proc/array.c
> @@ -530,18 +530,18 @@ static int do_task_stat(struct seq_file *m, struct pi=_namespace *ns,
> cgtime = sig->cgtime;
> = if (whole) {
> - struct task_struct *t = task;
> + struct task_struct *t;
> = min_flt = sig->min_flt;
> maj_flt = sig->maj_flt;
> gtime = sig->gtime;
> = rcu_read_lock();
> - do {
> + __for_each_thread(sig, t) {
> min_flt += t->min_flt;
> maj_flt += t->maj_flt;
> gtime += task_gtime(t);
> - } while_each_thread(task, t);
> + }
> rcu_read_unlock();
> }
> } while (need_seqretry(&sig->stats_lock, seq));
> -- =2.47.1
>
>
>
>
> Amazon Web Services Development Center Germany GmbH
> Tamara-Danz-Str. 13
> 10243 Berlin
> Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
> Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
> Sitz: Berlin
> Ust-ID: DE 365 538 597
>
>
next prev parent reply other threads:[~2025-07-09 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 14:07 Heyne, Maximilian
2025-07-09 12:03 ` Harshit Mogalapalli [this message]
2025-07-09 13:12 ` 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=ef0e0364-29e2-47c2-8f0a-93f385cebf08@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dssauerw@amazon.de \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mheyne@amazon.de \
--cc=oleg@redhat.com \
--cc=sashal@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®