public inbox for [email protected]
 help / color / mirror / Atom feed
From: syzbot <[email protected]>
To: [email protected], [email protected],
	[email protected], [email protected],
	[email protected]
Subject: Re: [syzbot] general protection fault in __io_queue_sqe
Date: Tue, 17 Aug 2021 01:19:12 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

syzbot has bisected this issue to:

commit 483fc4e30869f8bd1693aca9cffddb21fb303b32
Author: Pavel Begunkov <[email protected]>
Date:   Sun Aug 15 09:40:26 2021 +0000

    io_uring: optimise io_prep_linked_timeout()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16fada7e300000
start commit:   b9011c7e671d Add linux-next specific files for 20210816
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=15fada7e300000
console output: https://syzkaller.appspot.com/x/log.txt?x=11fada7e300000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a245d1aa4f055cc1
dashboard link: https://syzkaller.appspot.com/bug?extid=2b85e9379c34945fe38f
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17479216300000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=147f0111300000

Reported-by: [email protected]
Fixes: 483fc4e30869 ("io_uring: optimise io_prep_linked_timeout()")

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

      parent reply	other threads:[~2021-08-17  8:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 13:29 [syzbot] general protection fault in __io_queue_sqe syzbot
2021-08-16 21:41 ` syzbot
2021-08-16 21:49   ` Jens Axboe
2021-08-16 21:57     ` Jens Axboe
2021-08-16 22:50       ` Pavel Begunkov
2021-08-17  3:50       ` syzbot
2021-08-17  3:33     ` syzbot
2021-08-17  8:19 ` syzbot [this message]

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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