From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+5b4f4f81240931b16844@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] [mm?] INFO: rcu detected stall in wb_workfn (4)
Date: Wed, 3 Sep 2025 10:33:25 +0800 [thread overview]
Message-ID: <20250903023326.6389-1-hdanton@sina.com> (raw)
In-Reply-To: <68b70218.050a0220.3db4df.01d1.GAE@google.com>
> Date: Tue, 02 Sep 2025 07:41:28 -0700 [thread overview]
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: b320789d6883 Linux 6.17-rc4
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1406ae62580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=d4703ac89d9e185a
> dashboard link: https://syzkaller.appspot.com/bug?extid=5b4f4f81240931b16844
> compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=133b5e34580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1639ca42580000
#syz test upstream master
--- x/kernel/rcu/tree_stall.h
+++ y/kernel/rcu/tree_stall.h
@@ -590,8 +590,15 @@ static void rcu_check_gp_kthread_starvat
if (cpu_is_offline(cpu)) {
pr_err("RCU GP kthread last ran on offline CPU %d.\n", cpu);
} else if (!(data_race(READ_ONCE(rdp->mynode->qsmask)) & rdp->grpmask)) {
+ int i;
pr_err("Stack dump where RCU GP kthread last ran:\n");
dump_cpu_task(cpu);
+ for_each_online_cpu(i) {
+ if (i == cpu)
+ continue;
+ pr_err("Stack dump on CPU%d\n", i);
+ dump_cpu_task(i);
+ }
}
wake_up_process(gpk);
}
--
next prev parent reply other threads:[~2025-09-03 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 13:28 [syzbot] " syzbot
2025-09-02 14:41 ` [syzbot] [block?] " syzbot
2025-09-03 2:33 ` Hillf Danton [this message]
2025-09-03 3:12 ` syzbot
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=20250903023326.6389-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+5b4f4f81240931b16844@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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®