Linux-USB Archive on
 help / color / Atom feed
From: Eric Biggers <>
To: Greg Kroah-Hartman <>
	Andrey Konovalov <>,
	Alan Stern <>,
	Oliver Neukum <>
Subject: Re: Reminder: 52 active syzbot reports in usb subsystem
Date: Thu, 19 Sep 2019 10:32:49 -0700
Message-ID: <20190919173249.GD667@sol.localdomain> (raw)
In-Reply-To: <>

On Thu, Sep 19, 2019 at 08:40:58AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Sep 18, 2019 at 10:23:42PM -0700, Eric Biggers wrote:
> > [This email was generated by a script.  Let me know if you have any suggestions
> > to make it better, or if you want it re-generated with the latest status.]
> > 
> > Of the syzbot reports that have (re-)occurred in the last 7 days, I've manually
> > marked 52 of them as possibly being bugs in the usb subsystem.  This category
> > mostly includes USB driver bugs, but it might include some core USB bugs too. 
> > I've listed these bug reports below.
> > 
> > If you believe a bug is no longer valid, please close it by sending a '#syz
> > fix', '#syz dup', or '#syz invalid' command in reply to the original thread, as
> > explained at
> > 
> > If you believe I misattributed a bug to the usb subsystem, please let me know
> > and (if possible) forward it to the correct place.
> > 
> > Note: in total, I've actually assigned 90 open syzbot reports to this subsystem.
> > But to help focus people's efforts, I've only listed the 52 that have
> > (re-)occurred in the last week.  Let me know if you want the full list.
> Thanks for doing all of this.  There's a load of syzbot usb open bugs
> right now, hopefully the huge majority of them will "auto close" now
> that a lot of USB fixes are merged in Linus's tree.
> Then we can sift through the rest to see what we have missed and wait
> for the next round of fuzzing that will happen, as the codepaths we have
> fixed up can now go deeper :)
> thanks,

AFAICS, only 2 syzbot bugs were fixed in the USB pull request for 5.4, and they
were already closed by syzbot before I sent this reminder, as it seems to close
bugs within a matter of hours.  So probably almost all of these bugs are still
valid.  I'd be glad to resend a refreshed list in a week or two, but if you're
expecting the number of open bugs (or even "active" bugs) to go down much by
itself, you may be disappointed :-(

- Eric

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19  5:23 Eric Biggers
2019-09-19  6:40 ` Greg Kroah-Hartman
2019-09-19 17:32   ` Eric Biggers [this message]
2019-09-19 19:01     ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2019-08-22  3:28 Eric Biggers

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190919173249.GD667@sol.localdomain \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-USB Archive on

Archives are clonable:
	git clone --mirror linux-usb/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-usb linux-usb/ \
	public-inbox-index linux-usb

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone