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: 292, name: kworker/u5:5
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
3 locks held by kworker/u5:5/292:
#0: ffff88801b768138 ((wq_completion)hci4#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
#1: ffff88803ff77d90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
#2: ffffffff8560c4a0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
CPU: 1 PID: 292 Comm: kworker/u5:5 Not tainted 6.5.0-rc4-next-20230801 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci4 hci_tx_work
Call Trace:
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
=============================
[ BUG: Invalid wait context ]
6.5.0-rc4-next-20230801 #1 Tainted: G W
-----------------------------
kworker/u5:5/292 is trying to lock:
ffff8880093a49b0 (&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:5/292:
#0: ffff88801b768138 ((wq_completion)hci4#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
#1: ffff88803ff77d90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
#2: ffffffff8560c4a0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
stack backtrace:
CPU: 1 PID: 292 Comm: kworker/u5:5 Tainted: G W 6.5.0-rc4-next-20230801 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci4 hci_tx_work
Call Trace:
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
audit: type=1400 audit(1690890235.359:11): avc: denied { watch_reads } for pid=4291 comm="syz-executor.5" path="/syzkaller-testdir699188876/syzkaller.eAvURz/8" dev="sda" ino=15982 scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=dir permissive=1
Bluetooth: hci4: link tx timeout
Bluetooth: hci4: killing stalled connection 10:aa:aa:aa:aa:aa
Bluetooth: hci0: link tx timeout
Bluetooth: hci0: 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: 287, name: kworker/u5:2
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
CPU: 1 PID: 287 Comm: kworker/u5:2 Tainted: G W 6.5.0-rc4-next-20230801 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci0 hci_tx_work
Call Trace:
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
Bluetooth: hci7: link tx timeout
Bluetooth: hci7: killing stalled connection 10:aa:aa:aa:aa:aa
Bluetooth: hci4: link tx timeout
Bluetooth: hci4: killing stalled connection 10:aa:aa:aa:aa:aa
Bluetooth: hci4: command 0x0406 tx timeout
Bluetooth: hci0: command 0x0406 tx timeout
Bluetooth: hci7: command 0x0406 tx timeout