BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 5031, name: kworker/u5:2
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
3 locks held by kworker/u5:2/5031:
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:20 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: raw_atomic64_set include/linux/atomic/atomic-arch-fallback.h:2608 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: raw_atomic_long_set include/linux/atomic/atomic-long.h:79 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:3196 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:678 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:705 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: process_one_work+0x96a/0x16f0 kernel/workqueue.c:2570
#1: ffffc9000344fd78 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x99e/0x16f0 kernel/workqueue.c:2574
#2: ffffffff8c9a64a0 (rcu_read_lock){....}-{1:2}, at: hci_link_tx_to net/bluetooth/hci_core.c:3412 [inline]
#2: ffffffff8c9a64a0 (rcu_read_lock){....}-{1:2}, at: __check_timeout net/bluetooth/hci_core.c:3567 [inline]
#2: ffffffff8c9a64a0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x1d4/0x4e0 net/bluetooth/hci_core.c:3547
CPU: 0 PID: 5031 Comm: kworker/u5:2 Not tainted 6.5.0-syzkaller-04808-g6c1b980a7e79 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: hci0 hci_tx_work
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x125/0x1b0 lib/dump_stack.c:106
__might_resched+0x3c3/0x5e0 kernel/sched/core.c:10187
__mutex_lock_common kernel/locking/mutex.c:580 [inline]
__mutex_lock+0xee/0x1340 kernel/locking/mutex.c:747
hci_cmd_sync_submit+0x3f/0x340 net/bluetooth/hci_sync.c:699
hci_cmd_sync_queue+0x79/0xa0 net/bluetooth/hci_sync.c:739
hci_abort_conn+0x15b/0x330 net/bluetooth/hci_conn.c:2928
hci_disconnect+0xc4/0x220 net/bluetooth/hci_conn.c:258
hci_link_tx_to net/bluetooth/hci_core.c:3421 [inline]
__check_timeout net/bluetooth/hci_core.c:3567 [inline]
__check_timeout+0x331/0x4e0 net/bluetooth/hci_core.c:3547
hci_sched_le net/bluetooth/hci_core.c:3750 [inline]
hci_tx_work+0x818/0x1d30 net/bluetooth/hci_core.c:3828
process_one_work+0xaa2/0x16f0 kernel/workqueue.c:2600
worker_thread+0x687/0x1110 kernel/workqueue.c:2751
kthread+0x33a/0x430 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:145
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
=============================
[ BUG: Invalid wait context ]
6.5.0-syzkaller-04808-g6c1b980a7e79 #0 Tainted: G W
-----------------------------
kworker/u5:2/5031 is trying to lock:
ffff8880787989b0 (&hdev->unregister_lock){+.+.}-{3:3}, at: hci_cmd_sync_submit+0x3f/0x340 net/bluetooth/hci_sync.c:699
other info that might help us debug this:
context-{4:4}
3 locks held by kworker/u5:2/5031:
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:20 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: raw_atomic64_set include/linux/atomic/atomic-arch-fallback.h:2608 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: raw_atomic_long_set include/linux/atomic/atomic-long.h:79 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:3196 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:678 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:705 [inline]
#0: ffff88802ba46938 ((wq_completion)hci0#2){+.+.}-{0:0}, at: process_one_work+0x96a/0x16f0 kernel/workqueue.c:2570
#1: ffffc9000344fd78 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x99e/0x16f0 kernel/workqueue.c:2574
#2: ffffffff8c9a64a0 (rcu_read_lock){....}-{1:2}, at: hci_link_tx_to net/bluetooth/hci_core.c:3412 [inline]
#2: ffffffff8c9a64a0 (rcu_read_lock){....}-{1:2}, at: __check_timeout net/bluetooth/hci_core.c:3567 [inline]
#2: ffffffff8c9a64a0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x1d4/0x4e0 net/bluetooth/hci_core.c:3547
stack backtrace:
CPU: 0 PID: 5031 Comm: kworker/u5:2 Tainted: G W 6.5.0-syzkaller-04808-g6c1b980a7e79 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: hci0 hci_tx_work
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
print_lock_invalid_wait_context kernel/locking/lockdep.c:4750 [inline]
check_wait_context kernel/locking/lockdep.c:4820 [inline]
__lock_acquire+0x1575/0x5de0 kernel/locking/lockdep.c:5086
lock_acquire kernel/locking/lockdep.c:5753 [inline]
lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5718
__mutex_lock_common kernel/locking/mutex.c:603 [inline]
__mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747
hci_cmd_sync_submit+0x3f/0x340 net/bluetooth/hci_sync.c:699
hci_cmd_sync_queue+0x79/0xa0 net/bluetooth/hci_sync.c:739
hci_abort_conn+0x15b/0x330 net/bluetooth/hci_conn.c:2928
hci_disconnect+0xc4/0x220 net/bluetooth/hci_conn.c:258
hci_link_tx_to net/bluetooth/hci_core.c:3421 [inline]
__check_timeout net/bluetooth/hci_core.c:3567 [inline]
__check_timeout+0x331/0x4e0 net/bluetooth/hci_core.c:3547
hci_sched_le net/bluetooth/hci_core.c:3750 [inline]
hci_tx_work+0x818/0x1d30 net/bluetooth/hci_core.c:3828
process_one_work+0xaa2/0x16f0 kernel/workqueue.c:2600
worker_thread+0x687/0x1110 kernel/workqueue.c:2751
kthread+0x33a/0x430 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:145
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304