All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f252f28df734e8521387@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] general protection fault in io_kill_timeouts
Date: Wed, 23 Mar 2022 11:47:13 -0700	[thread overview]
Message-ID: <00000000000066cd8205dae72838@google.com> (raw)
In-Reply-To: <000000000000a0506305dae664f2@google.com>

syzbot has bisected this issue to:

commit c9be622494c012d56c71e00cb90be841820c3e34
Author: Pavel Begunkov <asml.silence@gmail.com>
Date:   Mon Mar 21 22:02:20 2022 +0000

    io_uring: remove extra ifs around io_commit_cqring

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15a04739700000
start commit:   b61581ae229d Add linux-next specific files for 20220323
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=17a04739700000
console output: https://syzkaller.appspot.com/x/log.txt?x=13a04739700000
kernel config:  https://syzkaller.appspot.com/x/.config?x=def28433baf109ed
dashboard link: https://syzkaller.appspot.com/bug?extid=f252f28df734e8521387
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=117d3a43700000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15538925700000

Reported-by: syzbot+f252f28df734e8521387@syzkaller.appspotmail.com
Fixes: c9be622494c0 ("io_uring: remove extra ifs around io_commit_cqring")

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

  reply	other threads:[~2022-03-23 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 17:52 [syzbot] general protection fault in io_kill_timeouts syzbot
2022-03-23 18:47 ` syzbot [this message]
2022-03-23 19:35   ` Pavel Begunkov
2022-03-23 23:06     ` 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=00000000000066cd8205dae72838@google.com \
    --to=syzbot+f252f28df734e8521387@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 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.