From: Aleksandr Nogikh <nogikh@google.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: syzbot <syzbot+05c0f12a4d43d656817e@syzkaller.appspotmail.com>,
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: Wed, 4 Dec 2024 18:11:51 +0100 [thread overview]
Message-ID: <CANp29Y5U3oMc3jYkxmnfd_9YYvWK3TwUhAbhA111k57AYRLd+A@mail.gmail.com> (raw)
In-Reply-To: <1ce3a220-7f68-4a68-a76c-b37fdf9bfc70@kernel.dk>
Hi Jens,
Just in case:
Syzbot reported this commit as the result of the cause (bug origin)
bisection, not as the commit after which the problem was gone. So
(unless it actually is a fixing commit) reporting it back via #syz fix
is not correct.
--
Aleksandr
On Wed, Dec 4, 2024 at 6:07 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> #syz fix: io_uring/rsrc: get rid of the empty node and dummy_ubuf
>
> --
> Jens Axboe
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-bugs/1ce3a220-7f68-4a68-a76c-b37fdf9bfc70%40kernel.dk.
next prev parent reply other threads:[~2024-12-04 17:12 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
2024-12-04 17:07 ` Jens Axboe
2024-12-04 17:11 ` Aleksandr Nogikh [this message]
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=CANp29Y5U3oMc3jYkxmnfd_9YYvWK3TwUhAbhA111k57AYRLd+A@mail.gmail.com \
--to=nogikh@google.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+05c0f12a4d43d656817e@syzkaller.appspotmail.com \
--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