From: Jens Axboe <axboe@kernel.dk>
To: Aleksandr Nogikh <nogikh@google.com>
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 10:14:44 -0700 [thread overview]
Message-ID: <9e8ccb61-e77a-4354-a848-81242625658c@kernel.dk> (raw)
In-Reply-To: <CANp29Y5U3oMc3jYkxmnfd_9YYvWK3TwUhAbhA111k57AYRLd+A@mail.gmail.com>
On 12/4/24 10:11 AM, Aleksandr Nogikh wrote:
> 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.
The commit got fixed, and hence there isn't a good way to convey this
to syzbot as far as I can tell. Just marking the updated one as the
fixer seems to be the best/closest option.
Other option is to mark it as invalid, but that also doesn't seem right.
I'm fine doing whatever to get issues like this closed, but it's not
an uncommon thing to have a buggy commit that's not upstream yet be
fixed up and hence not have the issue anymore.
--
Jens Axboe
next prev parent reply other threads:[~2024-12-04 17:14 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
2024-12-04 17:14 ` Jens Axboe [this message]
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=9e8ccb61-e77a-4354-a848-81242625658c@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--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