From: Pavel Begunkov <asml.silence@gmail.com>
To: syzbot <syzbot+1eca5b0d7ac82b74d347@syzkaller.appspotmail.com>,
axboe@kernel.dk, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in io_uring_setup (2)
Date: Thu, 29 Apr 2021 18:55:59 +0100 [thread overview]
Message-ID: <8eec9ad4-3341-f136-0983-52f3c687f9da@gmail.com> (raw)
In-Reply-To: <00000000000014ec7c05c12012b1@google.com>
On 4/29/21 6:46 PM, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit eae071c9b4cefbcc3f985c5abf9a6e32c1608ca9
> Author: Pavel Begunkov <asml.silence@gmail.com>
> Date: Sun Apr 25 13:32:24 2021 +0000
>
> io_uring: prepare fixed rw for dynanic buffers
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f639edd00000
> start commit: d72cd4ad Merge tag 'scsi-misc' of git://git.kernel.org/pub..
> git tree: upstream
> final oops: https://syzkaller.appspot.com/x/report.txt?x=100e39edd00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=17f639edd00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=53fdf14defd48c56
> dashboard link: https://syzkaller.appspot.com/bug?extid=1eca5b0d7ac82b74d347
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15aeff43d00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1747117dd00000
>
> Reported-by: syzbot+1eca5b0d7ac82b74d347@syzkaller.appspotmail.com
> Fixes: eae071c9b4ce ("io_uring: prepare fixed rw for dynanic buffers")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz test: git://git.kernel.dk/linux-block io_uring-5.13
--
Pavel Begunkov
next prev parent reply other threads:[~2021-04-29 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 15:01 syzbot
2021-04-29 17:46 ` syzbot
2021-04-29 17:55 ` Pavel Begunkov [this message]
2021-04-29 18:15 ` syzbot
2021-05-07 19:41 ` Pavel Begunkov
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=8eec9ad4-3341-f136-0983-52f3c687f9da@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+1eca5b0d7ac82b74d347@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®