[syzbot] WARNING in usb_remove_ep_devs

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    7756f1d6 phy: qcom-qusb2: Add configuration for SM4250 and..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=15d03bac300000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8df8c74fda98ee5f
dashboard link: https://syzkaller.appspot.com/bug?extid=a0c54eb26c7b8130c9b9

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a0c54eb26c7b8130c9b9@xxxxxxxxxxxxxxxxxxxxxxxxx

usb 6-1: ath9k_htc: USB layer deinitialized
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 0 PID: 7255 at kernel/locking/mutex.c:941 __mutex_lock_common kernel/locking/mutex.c:941 [inline]
WARNING: CPU: 0 PID: 7255 at kernel/locking/mutex.c:941 __mutex_lock+0xb8d/0x1080 kernel/locking/mutex.c:1104
Modules linked in:
CPU: 0 PID: 7255 Comm: kworker/0:7 Not tainted 5.13.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: usb_hub_wq hub_event
RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:941 [inline]
RIP: 0010:__mutex_lock+0xb8d/0x1080 kernel/locking/mutex.c:1104
Code: 08 84 d2 0f 85 ab 04 00 00 8b 05 46 7c b6 02 85 c0 0f 85 8f f5 ff ff 48 c7 c6 60 3a 07 86 48 c7 c7 20 38 07 86 e8 22 77 d3 ff <0f> 0b e9 75 f5 ff ff 65 48 8b 1c 25 40 ef 01 00 be 08 00 00 00 48
RSP: 0018:ffffc9000566f810 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000040000 RSI: ffffffff812a6723 RDI: fffff52000acdef4
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: ffffffff814b9bef R11: 0000000000000000 R12: dffffc0000000000
R13: ffff888147adc120 R14: ffff88811a3e10a8 R15: ffff88810f5fe008
FS:  0000000000000000(0000) GS:ffff8881f6a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005635c64e9457 CR3: 000000013faf2000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 device_lock include/linux/device.h:763 [inline]
 device_del+0x9e/0xd40 drivers/base/core.c:3502
 device_unregister+0x22/0xc0 drivers/base/core.c:3573
 usb_remove_ep_devs+0x3e/0x80 drivers/usb/core/endpoint.c:188
 usb_disconnect.cold+0x4ab/0x791 drivers/usb/core/hub.c:2240
 hub_port_connect drivers/usb/core/hub.c:5151 [inline]
 hub_port_connect_change drivers/usb/core/hub.c:5440 [inline]
 port_event drivers/usb/core/hub.c:5586 [inline]
 hub_event+0x1c9c/0x4330 drivers/usb/core/hub.c:5668
 process_one_work+0x98d/0x1580 kernel/workqueue.c:2276
 worker_thread+0x64c/0x1120 kernel/workqueue.c:2422
 kthread+0x38c/0x460 kernel/kthread.c:313
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.