zd1211rw 1-1:0.96: error ioread32(CR_REG1): -11 ============================================ WARNING: possible recursive locking detected 5.16.0-rc5-syzkaller #0 Not tainted -------------------------------------------- kworker/0:4/4052 is trying to acquire lock: ffff888110505ed0 (&chip->mutex){+.+.}-{3:3}, at: zd_chip_disable_rxtx+0x1c/0x40 drivers/net/wireless/zydas/zd1211rw/zd_chip.c:1465 but task is already holding lock: ffff88811407ded0 (&chip->mutex){+.+.}-{3:3}, at: pre_reset+0x217/0x290 drivers/net/wireless/zydas/zd1211rw/zd_usb.c:1503 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&chip->mutex); lock(&chip->mutex); *** DEADLOCK *** May be due to missing lock nesting notation 6 locks held by kworker/0:4/4052: #0: ffff888103dc8538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline] #0: ffff888103dc8538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline] #0: ffff888103dc8538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1198 [inline] #0: ffff888103dc8538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:635 [inline] #0: ffff888103dc8538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:662 [inline] #0: ffff888103dc8538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x896/0x1690 kernel/workqueue.c:2269 #1: ffffc900021c7db0 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x8ca/0x1690 kernel/workqueue.c:2273 #2: ffff88810c0d6220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline] #2: ffff88810c0d6220 (&dev->mutex){....}-{3:3}, at: hub_event+0x1c1/0x4460 drivers/usb/core/hub.c:5671 #3: ffff8881181ee220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline] #3: ffff8881181ee220 (&dev->mutex){....}-{3:3}, at: __device_attach+0x7a/0x4a0 drivers/base/dd.c:944 #4: ffff88811804c1a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline] #4: ffff88811804c1a8 (&dev->mutex){....}-{3:3}, at: __device_attach+0x7a/0x4a0 drivers/base/dd.c:944 #5: ffff88811407ded0 (&chip->mutex){+.+.}-{3:3}, at: pre_reset+0x217/0x290 drivers/net/wireless/zydas/zd1211rw/zd_usb.c:1503 stack backtrace: CPU: 0 PID: 4052 Comm: kworker/0:4 Not tainted 5.16.0-rc5-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 print_deadlock_bug kernel/locking/lockdep.c:2956 [inline] check_deadlock kernel/locking/lockdep.c:2999 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire.cold+0x149/0x3ab 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 zd_chip_disable_rxtx+0x1c/0x40 drivers/net/wireless/zydas/zd1211rw/zd_chip.c:1465 zd_op_stop+0x60/0x190 drivers/net/wireless/zydas/zd1211rw/zd_mac.c:343 zd_usb_stop drivers/net/wireless/zydas/zd1211rw/zd_usb.c:1478 [inline] pre_reset+0x19d/0x290 drivers/net/wireless/zydas/zd1211rw/zd_usb.c:1501 usb_reset_device+0x37d/0x9a0 drivers/usb/core/hub.c:6101 probe+0x10f/0x590 drivers/net/wireless/zydas/zd1211rw/zd_usb.c:1370 usb_probe_interface+0x315/0x7f0 drivers/usb/core/driver.c:396 call_driver_probe drivers/base/dd.c:517 [inline] really_probe+0x245/0xcc0 drivers/base/dd.c:596 __driver_probe_device+0x338/0x4d0 drivers/base/dd.c:751 driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:781 __device_attach_driver+0x20b/0x2f0 drivers/base/dd.c:898 bus_for_each_drv+0x15f/0x1e0 drivers/base/bus.c:427 __device_attach+0x228/0x4a0 drivers/base/dd.c:969 bus_probe_device+0x1e4/0x290 drivers/base/bus.c:487 device_add+0xc17/0x1ee0 drivers/base/core.c:3394 usb_set_configuration+0x101e/0x1900 drivers/usb/core/message.c:2170 usb_generic_driver_probe+0xba/0x100 drivers/usb/core/generic.c:238 usb_probe_device+0xd9/0x2c0 drivers/usb/core/driver.c:293 call_driver_probe drivers/base/dd.c:517 [inline] really_probe+0x245/0xcc0 drivers/base/dd.c:596 __driver_probe_device+0x338/0x4d0 drivers/base/dd.c:751 driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:781 __device_attach_driver+0x20b/0x2f0 drivers/base/dd.c:898 bus_for_each_drv+0x15f/0x1e0 drivers/base/bus.c:427 __device_attach+0x228/0x4a0 drivers/base/dd.c:969 bus_probe_device+0x1e4/0x290 drivers/base/bus.c:487 device_add+0xc17/0x1ee0 drivers/base/core.c:3394 usb_new_device.cold+0x63f/0x108e drivers/usb/core/hub.c:2563 hub_port_connect drivers/usb/core/hub.c:5353 [inline] hub_port_connect_change drivers/usb/core/hub.c:5497 [inline] port_event drivers/usb/core/hub.c:5643 [inline] hub_event+0x23e5/0x4460 drivers/usb/core/hub.c:5725 process_one_work+0x9b2/0x1690 kernel/workqueue.c:2298 worker_thread+0x658/0x11f0 kernel/workqueue.c:2445 kthread+0x40b/0x500 kernel/kthread.c:327 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 zd1211rw 1-1:0.236: error ioread32(CR_REG1): -11 usb 1-1: reset high-speed USB device number 44 using dummy_hcd usb 1-1: Using ep0 maxpacket: 8 usb 1-1: device firmware changed zd1211rw 1-1:0.216: couldn't reset usb device. Error number -19 usb 1-1: USB disconnect, device number 44 usb 1-1: new high-speed USB device number 45 using dummy_hcd usb 1-1: Using ep0 maxpacket: 8 usb 1-1: New USB device found, idVendor=1b3d, idProduct=01bc, bcdDevice=5d.58 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1: Product: syz usb 1-1: Manufacturer: syz usb 1-1: SerialNumber: syz usb 1-1: config 0 descriptor?? ftdi_sio 1-1:0.0: FTDI USB Serial Device converter detected usb 1-1: Detected FT-X ftdi_sio ttyUSB0: Unable to read latency timer: -71 ftdi_sio ttyUSB0: Unable to write latency timer: -71 ftdi_sio 1-1:0.0: GPIO initialisation failed: -71 usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0 usb 1-1: USB disconnect, device number 45 ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 ftdi_sio 1-1:0.0: device disconnected usb 4-1: new high-speed USB device number 57 using dummy_hcd usb 4-1: Using ep0 maxpacket: 8 usb 4-1: config 1 has an invalid descriptor of length 0, skipping remainder of the config usb 4-1: config 1 has 1 interface, different from the descriptor's value: 3 usb 4-1: New USB device found, idVendor=1d6b, idProduct=0101, bcdDevice= 0.40 usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-1: Product: 軳章髬i鋌낔뽹⼗事滋곂 usb 4-1: Manufacturer: 䘇즮탲ꎾ힬₁쀐谶졄㟄쌷镱춲Ϸ∓滦쪨愍ꆂ氄衅䝎 usb 4-1: SerialNumber: Д usb 4-1: 0:2 : does not exist usb 4-1: USB disconnect, device number 57 usb 1-1: new high-speed USB device number 47 using dummy_hcd usb 1-1: Using ep0 maxpacket: 8 usb 1-1: New USB device found, idVendor=1b3d, idProduct=01bc, bcdDevice=5d.58 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1: Product: syz usb 1-1: Manufacturer: syz usb 1-1: SerialNumber: syz usb 1-1: config 0 descriptor?? ftdi_sio 1-1:0.0: FTDI USB Serial Device converter detected usb 1-1: Detected FT-X ftdi_sio ttyUSB0: Unable to read latency timer: -71 ftdi_sio ttyUSB0: Unable to write latency timer: -71 ftdi_sio 1-1:0.0: GPIO initialisation failed: -71 usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0 usb 1-1: USB disconnect, device number 47 ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 ftdi_sio 1-1:0.0: device disconnected