Bluetooth: hci4: link tx timeout
Bluetooth: hci4: killing stalled connection 10:aa:aa:aa:aa:aa
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 284, name: kworker/u5:3
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
3 locks held by kworker/u5:3/284:
 #0: ffff888014c8c138 ((wq_completion)hci4#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
 #1: ffff8880068b7d90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
 #2: ffffffff8560c2a0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
CPU: 0 PID: 284 Comm: kworker/u5:3 Not tainted 6.5.0-rc5-next-20230807 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci4 hci_tx_work
Call Trace:
 <TASK>
 dump_stack_lvl+0xc1/0xf0
 __might_resched+0x2f9/0x510
 __mutex_lock+0x9e/0x1a30
 hci_cmd_sync_submit+0x3b/0x2d0
 hci_cmd_sync_queue+0x7b/0xb0
 hci_disconnect+0x1c2/0x450
 __check_timeout+0x2cc/0x480
 hci_tx_work+0x11b1/0x1a70
 process_one_work+0xabf/0x1770
 worker_thread+0x64f/0x12a0
 kthread+0x33f/0x440
 ret_from_fork+0x2f/0x70
 ret_from_fork_asm+0x1b/0x30
 </TASK>

=============================
[ BUG: Invalid wait context ]
6.5.0-rc5-next-20230807 #1 Tainted: G        W         
-----------------------------
kworker/u5:3/284 is trying to lock:
ffff88803ea589b0 (&hdev->unregister_lock){+.+.}-{3:3}, at: hci_cmd_sync_submit+0x3b/0x2d0
other info that might help us debug this:
context-{4:4}
3 locks held by kworker/u5:3/284:
 #0: ffff888014c8c138 ((wq_completion)hci4#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
 #1: ffff8880068b7d90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
 #2: ffffffff8560c2a0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
stack backtrace:
CPU: 0 PID: 284 Comm: kworker/u5:3 Tainted: G        W          6.5.0-rc5-next-20230807 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci4 hci_tx_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x91/0xf0
 __lock_acquire+0x1605/0x6340
 lock_acquire+0x19a/0x4c0
 __mutex_lock+0x12a/0x1a30
 hci_cmd_sync_submit+0x3b/0x2d0
 hci_cmd_sync_queue+0x7b/0xb0
 hci_disconnect+0x1c2/0x450
 __check_timeout+0x2cc/0x480
 hci_tx_work+0x11b1/0x1a70
 process_one_work+0xabf/0x1770
 worker_thread+0x64f/0x12a0
 kthread+0x33f/0x440
 ret_from_fork+0x2f/0x70
 ret_from_fork_asm+0x1b/0x30
 </TASK>
loop3: detected capacity change from 0 to 39
syz-executor.3: attempt to access beyond end of device
loop3: rw=2049, sector=124, nr_sectors = 4 limit=39
Buffer I/O error on dev loop3, logical block 31, lost async page write
syz-executor.3: attempt to access beyond end of device
loop3: rw=2049, sector=124, nr_sectors = 4 limit=39
Buffer I/O error on dev loop3, logical block 31, lost async page write
syz-executor.3: attempt to access beyond end of device
loop3: rw=2049, sector=124, nr_sectors = 4 limit=39
Buffer I/O error on dev loop3, logical block 31, lost async page write
Bluetooth: hci4: command 0x0406 tx timeout