From: syzbot <syzbot+00e15cda746c5bc70e24@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
gregkh@linuxfoundation.org, hdanton@sina.com,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in io_ring_exit_work
Date: Fri, 06 Aug 2021 08:21:14 -0700 [thread overview]
Message-ID: <00000000000016db0205c8e5967e@google.com> (raw)
In-Reply-To: <0000000000005225a605bd97fa64@google.com>
syzbot has bisected this issue to:
commit 6c2450ae55656f6b0370bfd4cb52ec8a4ecd0916
Author: Pavel Begunkov <asml.silence@gmail.com>
Date: Tue Feb 23 12:40:22 2021 +0000
io_uring: allocate memory for overflowed CQEs
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=138a96e6300000
start commit: 8d4b477da1a8 Add linux-next specific files for 20210730
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=104a96e6300000
console output: https://syzkaller.appspot.com/x/log.txt?x=178a96e6300000
kernel config: https://syzkaller.appspot.com/x/.config?x=4adf4987f875c210
dashboard link: https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d5cd96300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1798471e300000
Reported-by: syzbot+00e15cda746c5bc70e24@syzkaller.appspotmail.com
Fixes: 6c2450ae5565 ("io_uring: allocate memory for overflowed CQEs")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-08-06 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 19:08 [syzbot] WARNING in io_ring_exit_work syzbot
2021-08-06 7:02 ` syzbot
2021-08-06 9:20 ` Pavel Begunkov
2021-08-06 10:33 ` syzbot
2021-08-06 15:21 ` syzbot [this message]
2023-05-29 7:58 ` [syzbot] [io-uring?] " syzbot
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=00000000000016db0205c8e5967e@google.com \
--to=syzbot+00e15cda746c5bc70e24@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=syzkaller-bugs@googlegroups.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 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.