All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6cb1e1ecb22a749ef8e8@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] [io-uring?] general protection fault in io_uring_show_fdinfo (2)
Date: Fri, 01 Nov 2024 15:13:06 -0700	[thread overview]
Message-ID: <67255272.050a0220.35b515.017b.GAE@google.com> (raw)
In-Reply-To: <67251dc5.050a0220.529b6.015d.GAE@google.com>

syzbot has bisected this issue to:

commit 661768085e99aad356ebc77d78ac41fd02eccbe3
Author: Jens Axboe <axboe@kernel.dk>
Date:   Wed Oct 30 15:51:58 2024 +0000

    io_uring/rsrc: get rid of the empty node and dummy_ubuf

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17631630580000
start commit:   f9f24ca362a4 Add linux-next specific files for 20241031
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=14e31630580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10e31630580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=328572ed4d152be9
dashboard link: https://syzkaller.appspot.com/bug?extid=6cb1e1ecb22a749ef8e8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14f92630580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=126b655f980000

Reported-by: syzbot+6cb1e1ecb22a749ef8e8@syzkaller.appspotmail.com
Fixes: 661768085e99 ("io_uring/rsrc: get rid of the empty node and dummy_ubuf")

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

  parent reply	other threads:[~2024-11-01 22:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 18:28 [syzbot] [io-uring?] general protection fault in io_uring_show_fdinfo (2) syzbot
2024-11-01 18:39 ` Jens Axboe
2024-11-01 19:02   ` syzbot
2024-11-01 22:13 ` syzbot [this message]
2024-12-04 17:08   ` 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=67255272.050a0220.35b515.017b.GAE@google.com \
    --to=syzbot+6cb1e1ecb22a749ef8e8@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.