From: syzbot <syzbot+d5b23b18d2f4feae8a67@syzkaller.appspotmail.com>
To: bigeasy@linutronix.de, bristot@redhat.com, bsegall@google.com,
dietmar.eggemann@arm.com, gor@linux.ibm.com, jgross@suse.com,
juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
mgorman@suse.de, mingo@kernel.org, mingo@redhat.com,
namit@vmware.com, peterz@infradead.org, rdunlap@infradead.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
vincent.guittot@linaro.org
Subject: Re: [syzbot] possible deadlock in wake_up_all_idle_cpus
Date: Sat, 16 Oct 2021 16:32:05 -0700 [thread overview]
Message-ID: <00000000000041567305ce80b8af@google.com> (raw)
In-Reply-To: <000000000000cf252605ce67014a@google.com>
syzbot has bisected this issue to:
commit 8850cb663b5cda04d33f9cfbc38889d73d3c8e24
Author: Peter Zijlstra <peterz@infradead.org>
Date: Tue Sep 21 20:16:02 2021 +0000
sched: Simplify wake_up_*idle*()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=117802fb300000
start commit: 7c832d2f9b95 Add linux-next specific files for 20211015
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=137802fb300000
console output: https://syzkaller.appspot.com/x/log.txt?x=157802fb300000
kernel config: https://syzkaller.appspot.com/x/.config?x=f6ac42766a768877
dashboard link: https://syzkaller.appspot.com/bug?extid=d5b23b18d2f4feae8a67
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e920fcb00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13b83d80b00000
Reported-by: syzbot+d5b23b18d2f4feae8a67@syzkaller.appspotmail.com
Fixes: 8850cb663b5c ("sched: Simplify wake_up_*idle*()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-10-16 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 16:51 [syzbot] possible deadlock in wake_up_all_idle_cpus syzbot
2021-10-16 18:07 ` syzbot
2021-10-16 23:32 ` syzbot [this message]
2021-10-19 19:08 ` Sebastian Andrzej Siewior
2021-10-19 20:27 ` Peter Zijlstra
2021-10-20 6:32 ` Sebastian Andrzej Siewior
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=00000000000041567305ce80b8af@google.com \
--to=syzbot+d5b23b18d2f4feae8a67@syzkaller.appspotmail.com \
--cc=bigeasy@linutronix.de \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gor@linux.ibm.com \
--cc=jgross@suse.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vincent.guittot@linaro.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.