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>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: [syzbot] general protection fault in gadget_setup
Date: Fri, 16 Apr 2021 11:29:49 -0400 [thread overview]
Message-ID: <20210416152949.GC42403@rowland.harvard.edu> (raw)
In-Reply-To: <CACT4Y+aYfVxcXYOHwheW7Wp2oYcKm_zumeASo57Dy7deDfZJKA@mail.gmail.com>
On Fri, Apr 16, 2021 at 09:21:12AM +0200, Dmitry Vyukov wrote:
> On Thu, Apr 15, 2021 at 10:59 PM Alan Stern <stern@rowland.harvard.edu> wrote:
> >
> > On Tue, Apr 13, 2021 at 07:11:11PM +0200, Dmitry Vyukov wrote:
> > > Yes, this is possible:
> > > http://bit.do/syzbot#syzkaller-reproducers
> >
> > That's not really what I had in mind. I don't want to spend the time
> > and effort installing syskaller on my own system; I want to tell syzbot
> > to run a particular syzkaller program (the one that originally led to
> > this bug report) on a patched kernel.
> >
> > The syzbot instructions say that it can test bugs with reproducers. The
> > problem here is that there doesn't seem to be any way to tell it to use
> > a particular syzkaller program as a reproducer.
>
> Hi Alan,
>
> This makes sense and I've found an existing feature request:
> https://github.com/google/syzkaller/issues/1611
> I've added a reference to this thread there.
Great! Thank you.
Alan Stern
next prev parent reply other threads:[~2021-04-16 15:29 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
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 [this message]
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=20210416152949.GC42403@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 \
--cc=syzkaller@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