From: Greg KH <gregkh@linuxfoundation.org>
To: syzbot <syzbot+c1b25598aa60dcd47e78@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: ath10k USB support is incomplete, don't expect anything to work!
Date: Thu, 9 May 2019 13:56:31 +0200 [thread overview]
Message-ID: <20190509115631.GB18400@kroah.com> (raw)
In-Reply-To: <000000000000a3ca70058872de7c@google.com>
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@syzkaller.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.
prev parent reply other threads:[~2019-05-09 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 11:37 syzbot
2019-05-09 11:56 ` Greg KH [this message]
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=20190509115631.GB18400@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreyknvl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+c1b25598aa60dcd47e78@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
all inboxes | Powered by JetHome®