====================================================== WARNING: possible circular locking dependency detected 5.16.0-rc1-next-20211118-syzkaller #0 Not tainted ------------------------------------------------------ kworker/0:0/5 is trying to acquire lock: ffff88801c95c468 (hcd->address0_mutex){+.+.}-{3:3}, at: usb_reset_and_verify_device+0x3ee/0xee0 drivers/usb/core/hub.c:5923 but task is already holding lock: ffff8881476f85c0 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3086 [inline] ffff8881476f85c0 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_port_resume+0x2a6/0x1950 drivers/usb/core/hub.c:3644 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&port_dev->status_lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:607 [inline] __mutex_lock+0x12f/0x12f0 kernel/locking/mutex.c:740 usb_lock_port drivers/usb/core/hub.c:3086 [inline] hub_port_connect drivers/usb/core/hub.c:5279 [inline] hub_port_connect_change drivers/usb/core/hub.c:5493 [inline] port_event drivers/usb/core/hub.c:5639 [inline] hub_event+0x21c1/0x4450 drivers/usb/core/hub.c:5721 process_one_work+0x9b2/0x1690 kernel/workqueue.c:2298 worker_thread+0x658/0x11f0 kernel/workqueue.c:2445 kthread+0x405/0x4f0 kernel/kthread.c:327 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 -> #0 (hcd->address0_mutex){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3063 [inline] check_prevs_add kernel/locking/lockdep.c:3186 [inline] validate_chain kernel/locking/lockdep.c:3801 [inline] __lock_acquire+0x2a07/0x54a0 kernel/locking/lockdep.c:5027 lock_acquire kernel/locking/lockdep.c:5637 [inline] lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602 __mutex_lock_common kernel/locking/mutex.c:607 [inline] __mutex_lock+0x12f/0x12f0 kernel/locking/mutex.c:740 usb_reset_and_verify_device+0x3ee/0xee0 drivers/usb/core/hub.c:5923 finish_port_resume drivers/usb/core/hub.c:3499 [inline] usb_port_resume+0x12f7/0x1950 drivers/usb/core/hub.c:3699 usb_generic_driver_resume+0x40/0xa0 drivers/usb/core/generic.c:305 usb_resume_device drivers/usb/core/driver.c:1288 [inline] usb_resume_both+0x627/0x8d0 drivers/usb/core/driver.c:1512 __rpm_callback+0xc9/0x330 drivers/base/power/runtime.c:377 rpm_callback+0x1da/0x220 drivers/base/power/runtime.c:504 rpm_resume+0xf5d/0x1bd0 drivers/base/power/runtime.c:879 __pm_runtime_resume+0xb7/0x170 drivers/base/power/runtime.c:1110 pm_runtime_get_sync include/linux/pm_runtime.h:393 [inline] usb_autoresume_device+0x1e/0x60 drivers/usb/core/driver.c:1705 usb_remote_wakeup+0x8b/0xe0 drivers/usb/core/hub.c:3723 hub_port_connect_change drivers/usb/core/hub.c:5479 [inline] port_event drivers/usb/core/hub.c:5639 [inline] hub_event+0x2d69/0x4450 drivers/usb/core/hub.c:5721 process_one_work+0x9b2/0x1690 kernel/workqueue.c:2298 worker_thread+0x658/0x11f0 kernel/workqueue.c:2445 kthread+0x405/0x4f0 kernel/kthread.c:327 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&port_dev->status_lock); lock(hcd->address0_mutex); lock(&port_dev->status_lock); lock(hcd->address0_mutex); *** DEADLOCK *** 5 locks held by kworker/0:0/5: #0: ffff8880121cb538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline] #0: ffff8880121cb538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline] #0: ffff8880121cb538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1198 [inline] #0: ffff8880121cb538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:635 [inline] #0: ffff8880121cb538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:662 [inline] #0: ffff8880121cb538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x896/0x1690 kernel/workqueue.c:2269 #1: ffffc90000ca7db0 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x8ca/0x1690 kernel/workqueue.c:2273 #2: ffff88801dbb5220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline] #2: ffff88801dbb5220 (&dev->mutex){....}-{3:3}, at: hub_event+0x1c1/0x4450 drivers/usb/core/hub.c:5667 #3: ffff8880762aa220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline] #3: ffff8880762aa220 (&dev->mutex){....}-{3:3}, at: usb_remote_wakeup+0x1f/0xe0 drivers/usb/core/hub.c:3720 #4: ffff8881476f85c0 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3086 [inline] #4: ffff8881476f85c0 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_port_resume+0x2a6/0x1950 drivers/usb/core/hub.c:3644 stack backtrace: CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 5.16.0-rc1-next-20211118-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: usb_hub_wq hub_event Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2143 check_prev_add kernel/locking/lockdep.c:3063 [inline] check_prevs_add kernel/locking/lockdep.c:3186 [inline] validate_chain kernel/locking/lockdep.c:3801 [inline] __lock_acquire+0x2a07/0x54a0 kernel/locking/lockdep.c:5027 lock_acquire kernel/locking/lockdep.c:5637 [inline] lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602 __mutex_lock_common kernel/locking/mutex.c:607 [inline] __mutex_lock+0x12f/0x12f0 kernel/locking/mutex.c:740 usb_reset_and_verify_device+0x3ee/0xee0 drivers/usb/core/hub.c:5923 finish_port_resume drivers/usb/core/hub.c:3499 [inline] usb_port_resume+0x12f7/0x1950 drivers/usb/core/hub.c:3699 usb_generic_driver_resume+0x40/0xa0 drivers/usb/core/generic.c:305 usb_resume_device drivers/usb/core/driver.c:1288 [inline] usb_resume_both+0x627/0x8d0 drivers/usb/core/driver.c:1512 __rpm_callback+0xc9/0x330 drivers/base/power/runtime.c:377 rpm_callback+0x1da/0x220 drivers/base/power/runtime.c:504 rpm_resume+0xf5d/0x1bd0 drivers/base/power/runtime.c:879 __pm_runtime_resume+0xb7/0x170 drivers/base/power/runtime.c:1110 pm_runtime_get_sync include/linux/pm_runtime.h:393 [inline] usb_autoresume_device+0x1e/0x60 drivers/usb/core/driver.c:1705 usb_remote_wakeup+0x8b/0xe0 drivers/usb/core/hub.c:3723 hub_port_connect_change drivers/usb/core/hub.c:5479 [inline] port_event drivers/usb/core/hub.c:5639 [inline] hub_event+0x2d69/0x4450 drivers/usb/core/hub.c:5721 process_one_work+0x9b2/0x1690 kernel/workqueue.c:2298 worker_thread+0x658/0x11f0 kernel/workqueue.c:2445 kthread+0x405/0x4f0 kernel/kthread.c:327 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 usb 6-1: USB disconnect, device number 2 usb 3-1: new high-speed USB device number 4 using dummy_hcd usb 3-1: device not accepting address 4, error -71 usb 3-1: new high-speed USB device number 5 using dummy_hcd usb 3-1: Using ep0 maxpacket: 8 usb 3-1: config 19 interface 0 altsetting 0 endpoint 0x1 has invalid wMaxPacketSize 0 usb 3-1: New USB device found, idVendor=0659, idProduct=0020, bcdDevice=ff.62 usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-1: Product: syz usb 3-1: Manufacturer: syz usb 3-1: SerialNumber: syz cxacru 3-1:19.0: submit of read urb for cm 0x90 failed (-8) usb 3-1: USB disconnect, device number 5