From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+ba74b85fa15fd7a96437@syzkaller.appspotmail.com>,
asml.silence@gmail.com, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [syzbot] general protection fault in __io_arm_poll_handler
Date: Fri, 3 Sep 2021 18:49:11 -0600 [thread overview]
Message-ID: <15a67989-9ad7-11ef-9472-8e16ca6ec11a@kernel.dk> (raw)
In-Reply-To: <000000000000f0da6305cb1feacb@google.com>
On 9/3/21 5:47 PM, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-and-tested-by: syzbot+ba74b85fa15fd7a96437@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 31efe48e io_uring: fix possible poll event lost in mul..
> git tree: git://git.kernel.dk/linux-block for-5.15/io_uring
> kernel config: https://syzkaller.appspot.com/x/.config?x=914bb805fa8e8da9
> dashboard link: https://syzkaller.appspot.com/bug?extid=ba74b85fa15fd7a96437
> compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.1
>
> Note: testing is done by a robot and is best-effort only.
Dmitry, I wonder if there's a way to have syzbot know about what it's
testing and be able to run the pending patches for that tree? I think
we're up to 4 reports now that are all just fallout from the same bug,
and where a patch has been queued up for a few days. Since they all look
different, I can't fault syzbot for thinking they are different, even if
they have the same root cause.
Any way we can make this situation better? I can't keep replying that we
should test the current branch, and it'd be a shame to have a ton of
dupes.
--
Jens Axboe
next prev parent reply other threads:[~2021-09-04 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 20:28 [syzbot] general protection fault in __io_arm_poll_handler syzbot
2021-09-03 20:38 ` Jens Axboe
2021-09-03 23:47 ` syzbot
2021-09-04 0:49 ` Jens Axboe [this message]
2022-05-20 8:41 ` Dmitry Vyukov
2022-05-20 12:53 ` Jens Axboe
2021-09-04 13:18 ` syzbot
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=15a67989-9ad7-11ef-9472-8e16ca6ec11a@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=dvyukov@google.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+ba74b85fa15fd7a96437@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;
as well as URLs for NNTP newsgroup(s).