From: syzbot <syzbot+db339689b2101f6f6071@syzkaller.appspotmail.com>
To: andreyknvl@google.com, gregkh@linuxfoundation.org,
ingrassia@epigenesys.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in usbhid_raw_request/usb_submit_urb (3)
Date: Thu, 23 Apr 2020 19:10:06 -0700 [thread overview]
Message-ID: <0000000000002e31b205a3ffddb6@google.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.2004232138280.2101-100000@netrider.rowland.org>
Hello,
syzbot has tested the proposed patch but the reproducer still triggered crash:
WARNING in usb_reset_and_verify_device
------------[ cut here ]------------
usb 1-1: Device reset
WARNING: CPU: 0 PID: 94 at drivers/usb/core/hub.c:5761 usb_reset_and_verify_device+0x37d/0xce0 drivers/usb/core/hub.c:5761
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 94 Comm: kworker/0:2 Not tainted 5.6.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events __usb_queue_reset_device
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0xef/0x16e lib/dump_stack.c:118
panic+0x2aa/0x6e1 kernel/panic.c:221
__warn.cold+0x2f/0x30 kernel/panic.c:582
report_bug+0x27b/0x2f0 lib/bug.c:195
fixup_bug arch/x86/kernel/traps.c:174 [inline]
fixup_bug arch/x86/kernel/traps.c:169 [inline]
do_error_trap+0x12b/0x1e0 arch/x86/kernel/traps.c:267
do_invalid_op+0x32/0x40 arch/x86/kernel/traps.c:286
invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1027
RIP: 0010:usb_reset_and_verify_device+0x37d/0xce0 drivers/usb/core/hub.c:5761
Code: 0f 84 9e 06 00 00 e8 82 89 df fd 49 8d bc 24 a8 00 00 00 e8 85 59 19 ff 4c 89 ea 48 c7 c7 e0 86 3b 86 48 89 c6 e8 2b 1a b4 fd <0f> 0b 4d 89 e5 4c 89 34 24 44 8b 74 24 3c 48 b8 00 00 00 00 00 fc
RSP: 0018:ffff8881d5d7fb98 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8881d4d70000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff812974dd RDI: ffffed103abaff65
RBP: 0000000000000000 R08: ffff8881d6b01880 R09: ffffed103b646248
R10: ffffed103b646247 R11: ffff8881db23123f R12: ffff8881d8f1e000
R13: ffff8881c9381900 R14: ffff8881d4ce5000 R15: ffff8881d8f1e560
usb_reset_device+0x4bb/0x960 drivers/usb/core/hub.c:5946
__usb_queue_reset_device+0x68/0x90 drivers/usb/core/message.c:1754
process_one_work+0x94b/0x1620 kernel/workqueue.c:2266
worker_thread+0x96/0xe20 kernel/workqueue.c:2412
kthread+0x318/0x420 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
Kernel Offset: disabled
Rebooting in 86400 seconds..
Tested on:
commit: 0fa84af8 Merge tag 'usb-serial-5.7-rc1' of https://git.ker..
git tree: https://github.com/google/kasan.git
console output: https://syzkaller.appspot.com/x/log.txt?x=10d0c580100000
kernel config: https://syzkaller.appspot.com/x/.config?x=6b9c154b0c23aecf
dashboard link: https://syzkaller.appspot.com/bug?extid=db339689b2101f6f6071
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=14ab96a0100000
next prev parent reply other threads:[~2020-04-24 2:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 13:04 WARNING in usbhid_raw_request/usb_submit_urb (3) syzbot
2020-04-01 20:49 ` syzbot
2020-04-02 15:35 ` Alan Stern
2020-04-02 15:53 ` syzbot
2020-04-02 15:57 ` Andrey Konovalov
2020-04-02 17:22 ` syzbot
2020-04-02 19:00 ` Alan Stern
2020-04-02 21:25 ` syzbot
2020-04-23 1:18 ` Alan Stern
2020-04-23 1:36 ` syzbot
2020-04-23 16:37 ` Alan Stern
2020-04-23 17:20 ` syzbot
2020-04-23 18:54 ` Alan Stern
2020-04-23 20:37 ` syzbot
2020-04-23 21:09 ` Alan Stern
2020-04-23 21:51 ` syzbot
2020-04-24 1:00 ` Alan Stern
2020-04-24 1:19 ` syzbot
2020-04-24 1:39 ` Alan Stern
2020-04-24 2:10 ` syzbot [this message]
2020-04-24 12:20 ` Alan Stern
2020-04-24 12:32 ` syzbot
2020-04-24 15:20 ` Alan Stern
2020-04-24 15:34 ` syzbot
2020-04-24 19:14 ` Alan Stern
2020-04-24 19:32 ` syzbot
2020-04-25 20:25 ` Alan Stern
2020-04-25 21:21 ` syzbot
2020-04-29 20:11 ` Alan Stern
2020-04-29 20:30 ` syzbot
2020-04-29 23:41 ` Alan Stern
2020-04-29 23:59 ` syzbot
2020-04-30 14:58 ` Alan Stern
2020-04-30 15:18 ` syzbot
2020-05-01 20:07 ` [PATCH] USB: core: Fix misleading driver bug report Alan Stern
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=0000000000002e31b205a3ffddb6@google.com \
--to=syzbot+db339689b2101f6f6071@syzkaller.appspotmail.com \
--cc=andreyknvl@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=ingrassia@epigenesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--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.