From: Alan Stern <stern@rowland.harvard.edu>
To: andreyknvl@google.com
Cc: gregkh@linuxfoundation.org, <gustavo@embeddedor.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
<syzkaller-bugs@googlegroups.com>
Subject: Re: INFO: task hung in usb_kill_urb
Date: Fri, 12 Apr 2019 15:46:25 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1904121540001.1283-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <0000000000006f1596058653d991@google.com>
Andrey:
It's really hard to tell just what's going on here.
On Fri, 12 Apr 2019, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 9a33b369 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan/tree/usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=14c4c1af200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=23e37f59d94ddd15
> dashboard link: https://syzkaller.appspot.com/bug?extid=d919b0f29d7b5a4994b9
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14410dbb200000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f0acd3200000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+d919b0f29d7b5a4994b9@syzkaller.appspotmail.com
>
> usb-fuzzer-gadget dummy_udc.0: failed to start USB fuzzer: -22
> usb-fuzzer-gadget dummy_udc.0: failed to start USB fuzzer: -22
> usb-fuzzer-gadget dummy_udc.0: failed to start USB fuzzer: -22
> usb-fuzzer-gadget dummy_udc.0: failed to start USB fuzzer: -22
> usb-fuzzer-gadget dummy_udc.0: failed to start USB fuzzer: -22
> INFO: task kworker/0:2:532 blocked for more than 143 seconds.
> Not tainted 5.1.0-rc4-319354-g9a33b36 #3
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> kworker/0:2 D26656 532 2 0x80000000
> Workqueue: usb_hub_wq hub_event
> Call Trace:
> schedule+0x8f/0x180 kernel/sched/core.c:3562
> usb_kill_urb drivers/usb/core/urb.c:695 [inline]
> usb_kill_urb+0x22a/0x2c0 drivers/usb/core/urb.c:687
> usb_start_wait_urb+0x257/0x4d0 drivers/usb/core/message.c:63
> usb_internal_control_msg drivers/usb/core/message.c:101 [inline]
> usb_control_msg+0x321/0x4a0 drivers/usb/core/message.c:152
It looks like something is stuck waiting for usb_kill_urb() to finish.
But what happened before that?
I can't tell from the reproducer source, because it uses a bunch of
special stuff you added in your usb-fuzzer tree.
Alan Stern
next prev parent reply other threads:[~2019-04-12 19:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 11:46 INFO: task hung in usb_kill_urb syzbot
2019-04-12 19:46 ` Alan Stern [this message]
2019-04-15 17:48 ` Andrey Konovalov
2019-04-15 18:06 ` Alan Stern
2019-04-15 18:39 ` Gustavo A. R. Silva
2019-04-15 19:00 ` Greg Kroah-Hartman
2019-04-15 19:35 ` Andrey Konovalov
[not found] <CAAeHK+wDEOpkuh0+OmPra3Yu8ri-8As82CyZ-1KyYC62AJkj1Q@mail.gmail.com>
2019-04-16 15:44 ` Alan Stern
2019-04-16 15:44 ` Alan Stern
2019-04-16 16:19 ` syzbot
2019-04-16 16:19 ` syzbot
2019-04-16 18:25 ` Alan Stern
2019-04-16 18:25 ` Alan Stern
2019-04-16 19:03 ` syzbot
2019-04-16 19:03 ` syzbot
2019-04-16 21:14 ` Alan Stern
2019-04-16 21:14 ` Alan Stern
2019-04-16 21:53 ` syzbot
2019-04-16 21:53 ` syzbot
2019-04-17 19:09 ` Alan Stern
2019-04-17 19:09 ` Alan Stern
2019-04-17 19:56 ` syzbot
2019-04-17 19:56 ` syzbot
2019-04-18 12:21 ` Andrey Konovalov
2019-04-18 12:21 ` Andrey Konovalov
2019-04-17 11:16 ` Andrey Konovalov
2019-04-17 11:16 ` Andrey Konovalov
2019-04-19 18:36 Alan Stern
2019-04-23 12:44 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=Pine.LNX.4.44L0.1904121540001.1283-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=andreyknvl@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.