BUG: workqueue leaked atomic, lock or RCU: kworker/u9:5[26018]
     preempt=0x00000000 lock=0->1 RCU=0->0 workfn=hci_rx_work
1 lock held by kworker/u9:5/26018:
 #0: ffff8880525c6518 (&chan->lock/1){+.+.}-{3:3}, at: l2cap_chan_lock include/net/bluetooth/l2cap.h:827 [inline]
 #0: ffff8880525c6518 (&chan->lock/1){+.+.}-{3:3}, at: l2cap_conless_channel net/bluetooth/l2cap_core.c:6764 [inline]
 #0: ffff8880525c6518 (&chan->lock/1){+.+.}-{3:3}, at: l2cap_recv_frame+0x7ce/0x10840 net/bluetooth/l2cap_core.c:6830
CPU: 0 UID: 0 PID: 26018 Comm: kworker/u9:5 Not tainted 6.10.0-syzkaller-12030-g66ebbdfdeb09 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Workqueue: hci1 hci_rx_work
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:93 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119
 process_one_work kernel/workqueue.c:3252 [inline]
 process_scheduled_works+0x1121/0x1830 kernel/workqueue.c:3312
 worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

======================================================
WARNING: possible circular locking dependency detected
6.10.0-syzkaller-12030-g66ebbdfdeb09 #0 Not tainted
------------------------------------------------------
kworker/u9:5/26018 is trying to acquire lock:
ffff88807a9d2948 ((wq_completion)hci8#2){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3206 [inline]
ffff88807a9d2948 ((wq_completion)hci8#2){+.+.}-{0:0}, at: process_scheduled_works+0x90a/0x1830 kernel/workqueue.c:3312

but task is already holding lock:
ffff8880525c6518 (&chan->lock/1){+.+.}-{3:3}, at: l2cap_chan_lock include/net/bluetooth/l2cap.h:827 [inline]
ffff8880525c6518 (&chan->lock/1){+.+.}-{3:3}, at: l2cap_conless_channel net/bluetooth/l2cap_core.c:6764 [inline]
ffff8880525c6518 (&chan->lock/1){+.+.}-{3:3}, at: l2cap_recv_frame+0x7ce/0x10840 net/bluetooth/l2cap_core.c:6830

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&chan->lock/1){+.+.}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5759
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
       l2cap_chan_lock include/net/bluetooth/l2cap.h:827 [inline]
       l2cap_conless_channel net/bluetooth/l2cap_core.c:6764 [inline]
       l2cap_recv_frame+0x7ce/0x10840 net/bluetooth/l2cap_core.c:6830
       hci_acldata_packet net/bluetooth/hci_core.c:3797 [inline]
       hci_rx_work+0x50f/0xca0 net/bluetooth/hci_core.c:4034
       process_one_work kernel/workqueue.c:3231 [inline]
       process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312
       worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
       kthread+0x2f0/0x390 kernel/kthread.c:389
       ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

-> #1 ((work_completion)(&hdev->rx_work)){+.+.}-{0:0}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5759
       process_one_work kernel/workqueue.c:3207 [inline]
       process_scheduled_works+0x963/0x1830 kernel/workqueue.c:3312
       worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
       kthread+0x2f0/0x390 kernel/kthread.c:389
       ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

-> #0 ((wq_completion)hci8#2){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3133 [inline]
       check_prevs_add kernel/locking/lockdep.c:3252 [inline]
       validate_chain+0x18e0/0x5900 kernel/locking/lockdep.c:3868
       __lock_acquire+0x137a/0x2040 kernel/locking/lockdep.c:5142
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5759
       process_one_work kernel/workqueue.c:3206 [inline]
       process_scheduled_works+0x91f/0x1830 kernel/workqueue.c:3312
       worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
       kthread+0x2f0/0x390 kernel/kthread.c:389
       ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

other info that might help us debug this:

Chain exists of:
  (wq_completion)hci8#2 --> (work_completion)(&hdev->rx_work) --> &chan->lock/1

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&chan->lock/1);
                               lock((work_completion)(&hdev->rx_work));
                               lock(&chan->lock/1);
  lock((wq_completion)hci8#2);

 *** DEADLOCK ***

1 lock held by kworker/u9:5/26018:
 #0: ffff8880525c6518 (&chan->lock/1){+.+.}-{3:3}, at: l2cap_chan_lock include/net/bluetooth/l2cap.h:827 [inline]
 #0: ffff8880525c6518 (&chan->lock/1){+.+.}-{3:3}, at: l2cap_conless_channel net/bluetooth/l2cap_core.c:6764 [inline]
 #0: ffff8880525c6518 (&chan->lock/1){+.+.}-{3:3}, at: l2cap_recv_frame+0x7ce/0x10840 net/bluetooth/l2cap_core.c:6830

stack backtrace:
CPU: 0 UID: 0 PID: 26018 Comm: kworker/u9:5 Not tainted 6.10.0-syzkaller-12030-g66ebbdfdeb09 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Workqueue: hci8 hci_conn_timeout
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:93 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119
 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2186
 check_prev_add kernel/locking/lockdep.c:3133 [inline]
 check_prevs_add kernel/locking/lockdep.c:3252 [inline]
 validate_chain+0x18e0/0x5900 kernel/locking/lockdep.c:3868
 __lock_acquire+0x137a/0x2040 kernel/locking/lockdep.c:5142
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5759
 process_one_work kernel/workqueue.c:3206 [inline]
 process_scheduled_works+0x91f/0x1830 kernel/workqueue.c:3312
 worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
BUG: workqueue leaked atomic, lock or RCU: kworker/u9:5[26018]
     preempt=0x00000000 lock=1->0 RCU=0->0 workfn=hci_conn_timeout
INFO: lockdep is turned off.
CPU: 0 UID: 0 PID: 26018 Comm: kworker/u9:5 Not tainted 6.10.0-syzkaller-12030-g66ebbdfdeb09 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Workqueue: hci8 hci_conn_timeout
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:93 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119
 process_one_work kernel/workqueue.c:3252 [inline]
 process_scheduled_works+0x1121/0x1830 kernel/workqueue.c:3312
 worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Bluetooth: hci8: command 0x041b tx timeout