From: syzbot <syzbot+eec403943a2a2455adaa@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: rcu detected stall in gc_worker (3)
Date: Sun, 31 Jul 2022 03:09:16 -0700 [thread overview]
Message-ID: <0000000000006b309205e51713c7@google.com> (raw)
In-Reply-To: <20220731094805.847-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: rcu detected stall in corrupted
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...!: (1 GPs behind) idle=cad/1/0x4000000000000000 softirq=7023/7025 fqs=2
(detected by 1, t=10502 jiffies, g=7257, q=133)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4073 Comm: syz-executor.0 Not tainted 5.17.0-rc6-next-20220303-syzkaller-dirty #0
Harclient_loop: send disconnect: Broken pipe
Tested on:
commit: 91265a6d Add linux-next specific files for 20220303
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=166fe82e080000
kernel config: https://syzkaller.appspot.com/x/.config?x=617f79440a35673a
dashboard link: https://syzkaller.appspot.com/bug?extid=eec403943a2a2455adaa
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=15c240c1080000
next parent reply other threads:[~2022-07-31 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220731094805.847-1-hdanton@sina.com>
2022-07-31 10:09 ` syzbot [this message]
[not found] <20220731081548.659-1-hdanton@sina.com>
2022-07-31 8:31 ` [syzbot] INFO: rcu detected stall in gc_worker (3) syzbot
[not found] <20220731074633.519-1-hdanton@sina.com>
2022-07-31 8:03 ` syzbot
[not found] <20220321063053.2877-1-hdanton@sina.com>
2022-03-21 6:43 ` syzbot
[not found] ` <20220321080843.3060-1-hdanton@sina.com>
2022-03-21 21:01 ` Paul E. McKenney
[not found] <20220321031535.2804-1-hdanton@sina.com>
2022-03-21 3:23 ` syzbot
[not found] <20220321012046.2729-1-hdanton@sina.com>
2022-03-21 1:32 ` syzbot
[not found] <20220320152154.2662-1-hdanton@sina.com>
2022-03-20 15:33 ` syzbot
2022-03-20 12:02 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=0000000000006b309205e51713c7@google.com \
--to=syzbot+eec403943a2a2455adaa@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.