[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190509115631.GB18400@kroah.com>
Date: Thu, 9 May 2019 13:56:31 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: syzbot <syzbot+c1b25598aa60dcd47e78@...kaller.appspotmail.com>
Cc: andreyknvl@...gle.com, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: WARNING: ath10k USB support is incomplete, don't expect anything
to work!
On Thu, May 09, 2019 at 04:37:06AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 43151d6c 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=178c8394a00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=4183eeef650d1234
> dashboard link: https://syzkaller.appspot.com/bug?extid=c1b25598aa60dcd47e78
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c22222a00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ddce02a00000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+c1b25598aa60dcd47e78@...kaller.appspotmail.com
>
> usb 1-1: new low-speed USB device number 2 using dummy_hcd
> usb 1-1: config 0 has an invalid interface number: 93 but max is 0
> usb 1-1: config 0 has no interface number 0
> usb 1-1: New USB device found, idVendor=13b1, idProduct=0042,
> bcdDevice=f9.d4
> usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> usb 1-1: config 0 descriptor??
> usb 1-1: WARNING: ath10k USB support is incomplete, don't expect anything to
> work!
Looks like we just need to change the printk message string here.
Powered by blists - more mailing lists