From: syzbot <syzbot+05c0f12a4d43d656817e@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_sqe_buffer_register
Date: Sun, 03 Nov 2024 01:00:03 -0700 [thread overview]
Message-ID: <67272d83.050a0220.35b515.0198.GAE@google.com> (raw)
In-Reply-To: <67253504.050a0220.3c8d68.08e1.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=1586e987980000
start commit: f9f24ca362a4 Add linux-next specific files for 20241031
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1786e987980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1386e987980000
kernel config: https://syzkaller.appspot.com/x/.config?x=328572ed4d152be9
dashboard link: https://syzkaller.appspot.com/bug?extid=05c0f12a4d43d656817e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15abc6f7980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10eb655f980000
Reported-by: syzbot+05c0f12a4d43d656817e@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
next prev parent reply other threads:[~2024-11-03 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 20:07 [syzbot] [io-uring?] general protection fault in io_sqe_buffer_register syzbot
2024-11-01 20:29 ` Jens Axboe
2024-11-01 20:54 ` syzbot
2024-11-03 8:00 ` syzbot [this message]
2024-12-04 17:07 ` Jens Axboe
2024-12-04 17:11 ` Aleksandr Nogikh
2024-12-04 17:14 ` Jens Axboe
2024-12-04 17:34 ` Aleksandr Nogikh
2024-12-04 17:38 ` 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=67272d83.050a0220.35b515.0198.GAE@google.com \
--to=syzbot+05c0f12a4d43d656817e@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.