From: syzbot <syzbot+42670398d6ddb118138f@syzkaller.appspotmail.com>
To: aou@eecs.berkeley.edu, brauner@kernel.org, bristot@redhat.com,
bsegall@google.com, dietmar.eggemann@arm.com,
juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, mgorman@suse.de,
mingo@redhat.com, palmer@dabbelt.com, paul.walmsley@sifive.com,
peterz@infradead.org, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, vincent.guittot@linaro.org,
vschneid@redhat.com
Subject: [syzbot] riscv/fixes boot error: INFO: rcu detected stall in corrupted
Date: Tue, 14 Feb 2023 16:24:44 -0800 [thread overview]
Message-ID: <0000000000006bc5be05f4b21b7b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 950b879b7f02 riscv: Fixup race condition on PG_dcache_clea..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=137aaec0c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b3cd714c8e9a6e01
dashboard link: https://syzkaller.appspot.com/bug?extid=42670398d6ddb118138f
compiler: riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: riscv64
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+42670398d6ddb118138f@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...0: (1 GPs behind) idle=36ec/1/0x4000000000000000 softirq=6589/6590 fqs=9960
(detected by 1, t=30504 jiffies, g=14713, q=4 ncpus=2)
Task dump for CPU 0:
task:cmp state:R running task stack:0 pid:2746 ppid:2744 flags:0x00000008
Call Trace:
[<ffffffff834348b8>] context_switch kernel/sched/core.c:5244 [inline]
[<ffffffff834348b8>] __schedule+0x624/0x1254 kernel/sched/core.c:6555
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...0: (1 GPs behind) idle=36ec/1/0x4000000000000000 softirq=6589/6590 fqs=28261
(detected by 1, t=122009 jiffies, g=14713, q=4 ncpus=2)
Task dump for CPU 0:
task:cmp state:R running task stack:0 pid:2746 ppid:2744 flags:0x00000008
Call Trace:
[<ffffffff834348b8>] context_switch kernel/sched/core.c:5244 [inline]
[<ffffffff834348b8>] __schedule+0x624/0x1254 kernel/sched/core.c:6555
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-02-15 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 0:24 syzbot [this message]
2023-02-15 8:46 ` [syzbot] riscv/fixes boot error: INFO: rcu detected stall in corrupted Dmitry Vyukov
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=0000000000006bc5be05f4b21b7b@google.com \
--to=syzbot+42670398d6ddb118138f@syzkaller.appspotmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=brauner@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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