From: syzbot <syzbot+ea2f1484cffe5109dc10@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] WARNING in io_wqe_enqueue
Date: Fri, 04 Jun 2021 13:22:06 -0700 [thread overview]
Message-ID: <0000000000000bdfa905c3f6720f@google.com> (raw)
In-Reply-To: <0000000000006e1be105c3ed13fe@google.com>
syzbot has bisected this issue to:
commit 24369c2e3bb06d8c4e71fd6ceaf4f8a01ae79b7c
Author: Pavel Begunkov <asml.silence@gmail.com>
Date: Tue Jan 28 00:15:48 2020 +0000
io_uring: add io-wq workqueue sharing
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17934777d00000
start commit: f88cd3fb Merge tag 'vfio-v5.13-rc5' of git://github.com/aw..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14534777d00000
console output: https://syzkaller.appspot.com/x/log.txt?x=10534777d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=82d85e75046e5e64
dashboard link: https://syzkaller.appspot.com/bug?extid=ea2f1484cffe5109dc10
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16d5772fd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10525947d00000
Reported-by: syzbot+ea2f1484cffe5109dc10@syzkaller.appspotmail.com
Fixes: 24369c2e3bb0 ("io_uring: add io-wq workqueue sharing")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-06-04 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 9:11 [syzbot] WARNING in io_wqe_enqueue syzbot
2021-06-04 9:22 ` syzbot
2021-06-04 20:22 ` syzbot [this message]
2021-06-08 9:47 ` Hao Xu
2021-06-08 12:01 ` Dmitry Vyukov
2021-06-10 3:03 ` Hao Xu
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=0000000000000bdfa905c3f6720f@google.com \
--to=syzbot+ea2f1484cffe5109dc10@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.