From: syzbot <syzbot+3e3d9bd0c6ce9efbc3ef@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, mingo@redhat.com, peterz@infradead.org,
rostedt@goodmis.org, stable@vger.kernel.org,
syzkaller-bugs@googlegroups.com, will@kernel.org
Subject: Re: WARNING in io_uring_cancel_task_requests
Date: Thu, 28 Jan 2021 17:38:06 -0800 [thread overview]
Message-ID: <000000000000512a7f05ba000ead@google.com> (raw)
In-Reply-To: <000000000000619ae405b9f8cf6e@google.com>
syzbot has bisected this issue to:
commit 4d004099a668c41522242aa146a38cc4eb59cb1e
Author: Peter Zijlstra <peterz@infradead.org>
Date: Fri Oct 2 09:04:21 2020 +0000
lockdep: Fix lockdep recursion
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=133f3090d00000
start commit: d03154e8 Add linux-next specific files for 20210128
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10bf3090d00000
console output: https://syzkaller.appspot.com/x/log.txt?x=173f3090d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6953ffb584722a1
dashboard link: https://syzkaller.appspot.com/bug?extid=3e3d9bd0c6ce9efbc3ef
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a924c4d00000
Reported-by: syzbot+3e3d9bd0c6ce9efbc3ef@syzkaller.appspotmail.com
Fixes: 4d004099a668 ("lockdep: Fix lockdep recursion")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-01-29 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 16:59 WARNING in io_uring_cancel_task_requests syzbot
2021-01-28 17:18 ` Pavel Begunkov
2021-01-28 22:17 ` syzbot
2021-01-29 1:38 ` 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=000000000000512a7f05ba000ead@google.com \
--to=syzbot+3e3d9bd0c6ce9efbc3ef@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox