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:34:00 -0600 [thread overview]
Message-ID: <8cf1ef4e-03b6-4da2-530f-65058c57a9d1@kernel.dk> (raw)
In-Reply-To: <00000000000093a60105df3918eb@google.com>
On 5/17/22 12:13 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 42226c989789 Linux 5.18-rc7
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=125b807ef00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=902c5209311d387c
> dashboard link: https://syzkaller.appspot.com/bug?extid=1a0a53300ce782f8b3ad
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=149eb59ef00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17cc57c6f00000
>
> The issue was bisected to:
>
> commit 3f1d52abf098c85b177b8c6f5b310e8347d1bc42
> Author: Jens Axboe <axboe@kernel.dk>
> Date: Tue Mar 29 16:43:56 2022 +0000
>
> io_uring: defer msg-ring file validity check until command issue
#syz test git://git.kernel.dk/linux-block io_uring-5.18
--
Jens Axboe
next prev parent reply other threads:[~2022-05-17 18:34 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 [this message]
2022-05-17 18:44 ` syzbot
2022-05-17 18:46 ` Jens Axboe
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=8cf1ef4e-03b6-4da2-530f-65058c57a9d1@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 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.