Bluetooth: hci6: link tx timeout
Bluetooth: hci6: 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: 299, name: kworker/u5:9
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
3 locks held by kworker/u5:9/299:
#0: ffff888015983138 ((wq_completion)hci6#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
#1: ffff88803fde7d90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
#2: ffffffff8560c3e0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
CPU: 1 PID: 299 Comm: kworker/u5:9 Not tainted 6.5.0-rc3-next-20230724 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci6 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-rc3-next-20230724 #1 Tainted: G W
-----------------------------
kworker/u5:9/299 is trying to lock:
ffff88800d58c9b0 (&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:9/299:
#0: ffff888015983138 ((wq_completion)hci6#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
#1: ffff88803fde7d90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
#2: ffffffff8560c3e0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
stack backtrace:
CPU: 1 PID: 299 Comm: kworker/u5:9 Tainted: G W 6.5.0-rc3-next-20230724 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci6 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
Bluetooth: hci6: link tx timeout
Bluetooth: hci6: killing stalled connection 10:aa:aa:aa:aa:aa
Bluetooth: hci6: link tx timeout
Bluetooth: hci6: killing stalled connection 10:aa:aa:aa:aa:aa
Bluetooth: hci2: link tx timeout
Bluetooth: hci2: 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: 289, name: kworker/u5:3
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
CPU: 0 PID: 289 Comm: kworker/u5:3 Tainted: G W 6.5.0-rc3-next-20230724 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci2 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: hci3: link tx timeout
Bluetooth: hci3: killing stalled connection 10:aa:aa:aa:aa:aa
process 'syz-executor.7' launched './file1' with NULL argv: empty string added
Bluetooth: hci6: command 0x0406 tx timeout
EXT4-fs (sda): can't enable nombcache during remount
EXT4-fs (sda): can't enable nombcache during remount
EXT4-fs (sda): can't enable nombcache during remount
EXT4-fs (sda): can't enable nombcache during remount
Bluetooth: hci2: command 0x0406 tx timeout
EXT4-fs (sda): can't enable nombcache during remount
Bluetooth: hci3: command 0x0406 tx timeout
EXT4-fs (sda): can't enable nombcache during remount
EXT4-fs (sda): can't enable nombcache during remount
EXT4-fs (sda): can't enable nombcache during remount
loop3: detected capacity change from 0 to 5392
loop3: detected capacity change from 0 to 5392
loop3: detected capacity change from 0 to 5392
loop3: detected capacity change from 0 to 5392
Bluetooth: hci4: unexpected event 0x48 length: 29 > 3
Bluetooth: hci4: wrong event for mode 0
Bluetooth: hci4: hardware error 0x3f
Bluetooth: hci4: unexpected event 0x48 length: 29 > 3
Bluetooth: hci4: wrong event for mode 0
Bluetooth: hci4: unexpected event for opcode 0x2024
Zero length message leads to an empty skb
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pid=6754 comm=syz-executor.1
Bluetooth: Unexpected continuation frame (len 10)
Bluetooth: hci4: unexpected event 0x48 length: 29 > 3
Bluetooth: hci4: wrong event for mode 0
Bluetooth: hci4: unexpected event for opcode 0x2024
Bluetooth: hci4: unexpected event 0x48 length: 29 > 3
Bluetooth: hci4: wrong event for mode 0
Bluetooth: hci4: unexpected event for opcode 0x2024
Bluetooth: Unexpected continuation frame (len 10)
Bluetooth: hci4: unexpected event 0x48 length: 29 > 3
Bluetooth: hci4: wrong event for mode 0
Bluetooth: hci4: unexpected event for opcode 0x2024
Bluetooth: Unexpected continuation frame (len 10)
Bluetooth: Unexpected continuation frame (len 10)
Bluetooth: Unexpected continuation frame (len 10)
Bluetooth: Unexpected continuation frame (len 10)
Bluetooth: Unexpected continuation frame (len 10)
Bluetooth: Unexpected continuation frame (len 10)
Bluetooth: hci4: Opcode 0x c03 failed: -110
Bluetooth: hci4: hardware error 0x3f