linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+726f2ce6dbbf2ad8d133@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
	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 kiocb_done
Date: Sun, 03 Oct 2021 00:34:08 -0700	[thread overview]
Message-ID: <00000000000062ec7d05cd6dd2f6@google.com> (raw)
In-Reply-To: <0000000000000d4da305cb1d2467@google.com>

syzbot suspects this issue was fixed by commit:

commit b8ce1b9d25ccf81e1bbabd45b963ed98b2222df8
Author: Pavel Begunkov <asml.silence@gmail.com>
Date:   Tue Aug 31 13:13:11 2021 +0000

    io_uring: don't submit half-prepared drain request

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17b14b67300000
start commit:   4ac6d90867a4 Merge tag 'docs-5.15' of git://git.lwn.net/li..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=3c3a5498e99259cf
dashboard link: https://syzkaller.appspot.com/bug?extid=726f2ce6dbbf2ad8d133
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=124a3b49300000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=142e610b300000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: io_uring: don't submit half-prepared drain request

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2021-10-03  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 20:28 [syzbot] BUG: unable to handle kernel NULL pointer dereference in kiocb_done syzbot
2021-09-03 20:38 ` Jens Axboe
2021-09-03 23:08   ` syzbot
2021-10-03  7:34 ` syzbot [this message]
2021-10-03 13:05   ` Jens Axboe

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=00000000000062ec7d05cd6dd2f6@google.com \
    --to=syzbot+726f2ce6dbbf2ad8d133@syzkaller.appspotmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).