From: Alan Stern <stern@rowland.harvard.edu>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+eb4674092e6cc8d9e0bd@syzkaller.appspotmail.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Felipe Balbi <balbi@kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] general protection fault in gadget_setup
Date: Tue, 13 Apr 2021 12:57:24 -0400 [thread overview]
Message-ID: <20210413165724.GD1454681@rowland.harvard.edu> (raw)
In-Reply-To: <CACT4Y+YEw4iJPxY4b6LPXrU91TODfu09dG=53exvQkwjPBg23w@mail.gmail.com>
On Tue, Apr 13, 2021 at 06:47:47PM +0200, Dmitry Vyukov wrote:
> On Tue, Apr 13, 2021 at 6:13 PM Alan Stern <stern@rowland.harvard.edu> wrote:
> > Hopefully this patch will make the race a lot more likely to occur. Is
> > there any way to tell syzkaller to test it, despite the fact that
> > syzkaller doesn't think it has a reproducer for this issue?
>
> If there is no reproducer the only way syzbot can test it is if it's
> in linux-next under CONFIG_DEBUG_AID_FOR_SYZBOT:
> http://bit.do/syzbot#no-custom-patches
There _is_ a theoretical reproducer: the test that provoked syzkaller's
original bug report. But syzkaller doesn't realize that it is (or may
be) a reproducer.
It ought to be possible to ask syzkaller to run a particular test that
it has done before, with a patch applied -- and without having to add
anything to linux-next.
Alan Stern
next prev parent reply other threads:[~2021-04-13 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 8:08 [syzbot] general protection fault in gadget_setup syzbot
2021-04-13 8:12 ` Dmitry Vyukov
2021-04-13 16:13 ` Alan Stern
2021-04-13 16:47 ` Dmitry Vyukov
2021-04-13 16:57 ` Alan Stern [this message]
2021-04-13 17:11 ` Dmitry Vyukov
2021-04-15 20:59 ` Alan Stern
2021-04-16 7:21 ` Dmitry Vyukov
2021-04-16 15:29 ` Alan Stern
2021-04-16 5:40 ` Anirudh Rayabharam
2021-04-16 15:27 ` Alan Stern
2021-04-16 17:05 ` Anirudh Rayabharam
2021-04-16 17:46 ` Alan Stern
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=20210413165724.GD1454681@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=andreyknvl@gmail.com \
--cc=balbi@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+eb4674092e6cc8d9e0bd@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