linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrey Konovalov <andreyknvl@google.com>,
	syzbot <syzbot+dbd38fbb686a9681143a@syzkaller.appspotmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: general protection fault in open_rio
Date: Tue, 24 Sep 2019 16:38:04 +0200	[thread overview]
Message-ID: <20190924143804.GA623902@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1909241031550.6144-100000@netrider.rowland.org>

On Tue, Sep 24, 2019 at 10:33:12AM -0400, Alan Stern wrote:
> On Tue, 24 Sep 2019, Andrey Konovalov wrote:
> 
> > On Tue, Sep 24, 2019 at 4:19 PM syzbot
> > <syzbot+dbd38fbb686a9681143a@syzkaller.appspotmail.com> wrote:
> > >
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:    d9e63adc usb-fuzzer: main usb gadget fuzzer driver
> > > git tree:       https://github.com/google/kasan.git usb-fuzzer
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=1602b303600000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=f4fa60e981ee8e6a
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=dbd38fbb686a9681143a
> > > compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> > >
> > > Unfortunately, I don't have any reproducer for this crash yet.
> > >
> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > Reported-by: syzbot+dbd38fbb686a9681143a@syzkaller.appspotmail.com
> 
> > Most probably the same bug:
> > 
> > https://syzkaller.appspot.com/bug?extid=745b0dff8028f9488eba
> > 
> > #syz dup: KASAN: invalid-free in disconnect_rio (2)
> 
> Even more to the point, a patch was recently posted to the mailing list 
> to remove the rio500 driver entirely:
> 
> 	https://marc.info/?l=linux-usb&m=156925553004947&w=2

I'll be queueing this up and just marking the driver BROKEN on older
kernels to solve all of these issues :)

thanks,

greg k-h

  parent reply	other threads:[~2019-09-24 14:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 14:19 general protection fault in open_rio syzbot
2019-09-24 14:20 ` Andrey Konovalov
2019-09-24 14:33   ` Alan Stern
2019-09-24 14:35     ` Andrey Konovalov
2019-09-24 14:38     ` Greg Kroah-Hartman [this message]
2019-10-10 15:36       ` Andrey Konovalov

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=20190924143804.GA623902@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreyknvl@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=syzbot+dbd38fbb686a9681143a@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).