====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc4-syzkaller-gbf4807c89d8f #0 Not tainted ------------------------------------------------------ syz-executor/6665 is trying to acquire lock: ffff8880332d1840 ((work_completion)(&(&conn->info_timer)->work)){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline] ffff8880332d1840 ((work_completion)(&(&conn->info_timer)->work)){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline] ffff8880332d1840 ((work_completion)(&(&conn->info_timer)->work)){+.+.}-{0:0}, at: start_flush_work kernel/workqueue.c:4152 [inline] ffff8880332d1840 ((work_completion)(&(&conn->info_timer)->work)){+.+.}-{0:0}, at: __flush_work+0xd2/0xbc0 kernel/workqueue.c:4210 but task is already holding lock: ffff8880332d1b38 (&conn->lock#2){+.+.}-{4:4}, at: l2cap_conn_del+0x70/0x680 net/bluetooth/l2cap_core.c:1762 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&conn->lock#2){+.+.}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747 l2cap_info_timeout+0x60/0xa0 net/bluetooth/l2cap_core.c:1668 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 -> #0 ((work_completion)(&(&conn->info_timer)->work)){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 touch_work_lockdep_map kernel/workqueue.c:3924 [inline] start_flush_work kernel/workqueue.c:4178 [inline] __flush_work+0x6b8/0xbc0 kernel/workqueue.c:4210 __cancel_work_sync+0xbe/0x110 kernel/workqueue.c:4366 l2cap_conn_del+0x4f0/0x680 net/bluetooth/l2cap_core.c:1796 hci_disconn_cfm include/net/bluetooth/hci_core.h:2071 [inline] hci_conn_hash_flush+0x10d/0x230 net/bluetooth/hci_conn.c:2560 hci_dev_close_sync+0xaef/0x1330 net/bluetooth/hci_sync.c:5250 hci_dev_do_close net/bluetooth/hci_core.c:501 [inline] hci_unregister_dev+0x21a/0x510 net/bluetooth/hci_core.c:2717 vhci_release+0x80/0xd0 drivers/bluetooth/hci_vhci.c:665 __fput+0x449/0xa70 fs/file_table.c:465 task_work_run+0x1d1/0x260 kernel/task_work.c:227 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0x6b5/0x22e0 kernel/exit.c:964 do_group_exit+0x21c/0x2d0 kernel/exit.c:1105 __do_sys_exit_group kernel/exit.c:1116 [inline] __se_sys_exit_group kernel/exit.c:1114 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1114 x64_sys_call+0x21ba/0x21c0 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&conn->lock#2); lock((work_completion)(&(&conn->info_timer)->work)); lock(&conn->lock#2); lock((work_completion)(&(&conn->info_timer)->work)); *** DEADLOCK *** 5 locks held by syz-executor/6665: #0: ffff888034748dc0 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_do_close net/bluetooth/hci_core.c:499 [inline] #0: ffff888034748dc0 (&hdev->req_lock){+.+.}-{4:4}, at: hci_unregister_dev+0x212/0x510 net/bluetooth/hci_core.c:2717 #1: ffff8880347480b8 (&hdev->lock){+.+.}-{4:4}, at: hci_dev_close_sync+0x66a/0x1330 net/bluetooth/hci_sync.c:5238 #2: ffffffff8f6777e8 (hci_cb_list_lock){+.+.}-{4:4}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:2068 [inline] #2: ffffffff8f6777e8 (hci_cb_list_lock){+.+.}-{4:4}, at: hci_conn_hash_flush+0xa1/0x230 net/bluetooth/hci_conn.c:2560 #3: ffff8880332d1b38 (&conn->lock#2){+.+.}-{4:4}, at: l2cap_conn_del+0x70/0x680 net/bluetooth/l2cap_core.c:1762 #4: ffffffff8e13ee20 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline] #4: ffffffff8e13ee20 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline] #4: ffffffff8e13ee20 (rcu_read_lock){....}-{1:3}, at: start_flush_work kernel/workqueue.c:4152 [inline] #4: ffffffff8e13ee20 (rcu_read_lock){....}-{1:3}, at: __flush_work+0xd2/0xbc0 kernel/workqueue.c:4210 stack backtrace: CPU: 0 UID: 0 PID: 6665 Comm: syz-executor Not tainted 6.16.0-rc4-syzkaller-gbf4807c89d8f #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2046 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 touch_work_lockdep_map kernel/workqueue.c:3924 [inline] start_flush_work kernel/workqueue.c:4178 [inline] __flush_work+0x6b8/0xbc0 kernel/workqueue.c:4210 __cancel_work_sync+0xbe/0x110 kernel/workqueue.c:4366 l2cap_conn_del+0x4f0/0x680 net/bluetooth/l2cap_core.c:1796 hci_disconn_cfm include/net/bluetooth/hci_core.h:2071 [inline] hci_conn_hash_flush+0x10d/0x230 net/bluetooth/hci_conn.c:2560 hci_dev_close_sync+0xaef/0x1330 net/bluetooth/hci_sync.c:5250 hci_dev_do_close net/bluetooth/hci_core.c:501 [inline] hci_unregister_dev+0x21a/0x510 net/bluetooth/hci_core.c:2717 vhci_release+0x80/0xd0 drivers/bluetooth/hci_vhci.c:665 __fput+0x449/0xa70 fs/file_table.c:465 task_work_run+0x1d1/0x260 kernel/task_work.c:227 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0x6b5/0x22e0 kernel/exit.c:964 do_group_exit+0x21c/0x2d0 kernel/exit.c:1105 __do_sys_exit_group kernel/exit.c:1116 [inline] __se_sys_exit_group kernel/exit.c:1114 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1114 x64_sys_call+0x21ba/0x21c0 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fc99d18e929 Code: Unable to access opcode bytes at 0x7fc99d18e8ff. RSP: 002b:00007ffc8c66fa38 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc99d18e929 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000043 RBP: 00007fc99d1ee8f0 R08: 00007ffc8c66d7d7 R09: 0000000000000003 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 0000000000000003 R14: 00000000ffffffff R15: 00007ffc8c66fbf0