From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+1a0a53300ce782f8b3ad@syzkaller.appspotmail.com>,
asml.silence@gmail.com, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] BUG: unable to handle kernel NULL pointer dereference in io_do_iopoll
Date: Tue, 17 May 2022 12:46:40 -0600 [thread overview]
Message-ID: <b6f36795-97ac-fac0-ab07-98de8255e4f9@kernel.dk> (raw)
In-Reply-To: <000000000000c1bd6505df39865e@google.com>
On 5/17/22 12:44 PM, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> BUG: unable to handle kernel NULL pointer dereference in io_do_iopoll
Gah, backport ended up putting the hunk in the wrong spot, not very useful.
#syz test git://git.kernel.dk/linux-block io_uring-5.18
--
Jens Axboe
next prev parent reply other threads:[~2022-05-17 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 18:13 [syzbot] BUG: unable to handle kernel NULL pointer dereference in io_do_iopoll syzbot
2022-05-17 18:34 ` Jens Axboe
2022-05-17 18:44 ` syzbot
2022-05-17 18:46 ` Jens Axboe [this message]
2022-05-17 19:02 ` 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=b6f36795-97ac-fac0-ab07-98de8255e4f9@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+1a0a53300ce782f8b3ad@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