From: syzbot <syzbot+4b71bb3365e7d5228913@syzkaller•appspotmail.com>
To: acme@kernel•org, alexander.shishkin@linux•intel.com,
andrii@kernel•org, ast@kernel•org, bigeasy@linutronix•de,
bpf@vger•kernel.org, bristot@redhat•com, bsegall@google•com,
daniel@iogearbox•net, dietmar.eggemann@arm•com,
gor@linux•ibm.com, jgross@suse•com, john.fastabend@gmail•com,
jolsa@redhat•com, juri.lelli@redhat•com, kafai@fb•com,
kpsingh@kernel•org, linux-kernel@vger•kernel.org,
linux-perf-users@vger•kernel.org, mark.rutland@arm•com,
mgorman@suse•de, mingo@redhat•com, namhyung@kernel•org,
namit@vmware•com, netdev@vger•kernel.org, peterz@infradead•org,
rostedt@goodmis•org, songliubraving@fb•com,
syzkaller-bugs@googlegroups•com, vincent.guittot@linaro•org,
yhs@fb•com
Subject: Re: [syzbot] possible deadlock in perf_event_ctx_lock_nested (2)
Date: Tue, 19 Oct 2021 10:09:13 -0700 [thread overview]
Message-ID: <0000000000008578d105ceb7b82e@google.com> (raw)
In-Reply-To: <0000000000007e727005c284bc8e@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=166a8c90b00000
start commit: 60e8840126bd Add linux-next specific files for 20211018
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=156a8c90b00000
console output: https://syzkaller.appspot.com/x/log.txt?x=116a8c90b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4bd44cafcda7632e
dashboard link: https://syzkaller.appspot.com/bug?extid=4b71bb3365e7d5228913
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11eccf58b00000
Reported-by: syzbot+4b71bb3365e7d5228913@syzkaller•appspotmail.com
Fixes: 8850cb663b5c ("sched: Simplify wake_up_*idle*()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-10-19 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 11:17 [syzbot] possible deadlock in perf_event_ctx_lock_nested (2) syzbot
2021-10-19 12:50 ` syzbot
2021-10-19 17:09 ` syzbot [this message]
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=0000000000008578d105ceb7b82e@google.com \
--to=syzbot+4b71bb3365e7d5228913@syzkaller$(echo .)appspotmail.com \
--cc=acme@kernel$(echo .)org \
--cc=alexander.shishkin@linux$(echo .)intel.com \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bigeasy@linutronix$(echo .)de \
--cc=bpf@vger$(echo .)kernel.org \
--cc=bristot@redhat$(echo .)com \
--cc=bsegall@google$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=dietmar.eggemann@arm$(echo .)com \
--cc=gor@linux$(echo .)ibm.com \
--cc=jgross@suse$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=jolsa@redhat$(echo .)com \
--cc=juri.lelli@redhat$(echo .)com \
--cc=kafai@fb$(echo .)com \
--cc=kpsingh@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-perf-users@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=mgorman@suse$(echo .)de \
--cc=mingo@redhat$(echo .)com \
--cc=namhyung@kernel$(echo .)org \
--cc=namit@vmware$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=peterz@infradead$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=songliubraving@fb$(echo .)com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=vincent.guittot@linaro$(echo .)org \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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