====================================================== WARNING: possible circular locking dependency detected 6.15.0-syzkaller-12422-g2c7e4a2663a1 #0 Not tainted ------------------------------------------------------ syz-executor/5982 is trying to acquire lock: ffff8880791bf840 ((work_completion)(&(&conn->info_timer)->work)){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline] ffff8880791bf840 ((work_completion)(&(&conn->info_timer)->work)){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline] ffff8880791bf840 ((work_completion)(&(&conn->info_timer)->work)){+.+.}-{0:0}, at: start_flush_work kernel/workqueue.c:4152 [inline] ffff8880791bf840 ((work_completion)(&(&conn->info_timer)->work)){+.+.}-{0:0}, at: __flush_work+0xd2/0xbc0 kernel/workqueue.c:4210 but task is already holding lock: ffff8880791bfb38 (&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+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3f9/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:2065 [inline] hci_conn_hash_flush+0x10a/0x230 net/bluetooth/hci_conn.c:2543 hci_dev_close_sync+0xaef/0x1330 net/bluetooth/hci_sync.c:5225 hci_dev_do_close net/bluetooth/hci_core.c:483 [inline] hci_unregister_dev+0x206/0x500 net/bluetooth/hci_core.c:2678 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+0x6ad/0x22e0 kernel/exit.c:955 do_group_exit+0x21c/0x2d0 kernel/exit.c:1104 get_signal+0x1286/0x1340 kernel/signal.c:3034 arch_do_signal_or_restart+0x9a/0x750 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop+0x75/0x110 kernel/entry/common.c:111 exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:414 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:449 [inline] do_syscall_64+0x2bd/0x3b0 arch/x86/entry/syscall_64.c:100 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/5982: #0: ffff88806254cd80 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_do_close net/bluetooth/hci_core.c:481 [inline] #0: ffff88806254cd80 (&hdev->req_lock){+.+.}-{4:4}, at: hci_unregister_dev+0x1fe/0x500 net/bluetooth/hci_core.c:2678 #1: ffff88806254c078 (&hdev->lock){+.+.}-{4:4}, at: hci_dev_close_sync+0x66a/0x1330 net/bluetooth/hci_sync.c:5213 #2: ffffffff8f677668 (hci_cb_list_lock){+.+.}-{4:4}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:2062 [inline] #2: ffffffff8f677668 (hci_cb_list_lock){+.+.}-{4:4}, at: hci_conn_hash_flush+0xa1/0x230 net/bluetooth/hci_conn.c:2543 #3: ffff8880791bfb38 (&conn->lock#2){+.+.}-{4:4}, at: l2cap_conn_del+0x70/0x680 net/bluetooth/l2cap_core.c:1762 #4: ffffffff8e13f060 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline] #4: ffffffff8e13f060 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline] #4: ffffffff8e13f060 (rcu_read_lock){....}-{1:3}, at: start_flush_work kernel/workqueue.c:4152 [inline] #4: ffffffff8e13f060 (rcu_read_lock){....}-{1:3}, at: __flush_work+0xd2/0xbc0 kernel/workqueue.c:4210 stack backtrace: CPU: 1 UID: 0 PID: 5982 Comm: syz-executor Not tainted 6.15.0-syzkaller-12422-g2c7e4a2663a1 #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:2065 [inline] hci_conn_hash_flush+0x10a/0x230 net/bluetooth/hci_conn.c:2543 hci_dev_close_sync+0xaef/0x1330 net/bluetooth/hci_sync.c:5225 hci_dev_do_close net/bluetooth/hci_core.c:483 [inline] hci_unregister_dev+0x206/0x500 net/bluetooth/hci_core.c:2678 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+0x6ad/0x22e0 kernel/exit.c:955 do_group_exit+0x21c/0x2d0 kernel/exit.c:1104 get_signal+0x1286/0x1340 kernel/signal.c:3034 arch_do_signal_or_restart+0x9a/0x750 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop+0x75/0x110 kernel/entry/common.c:111 exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:414 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:449 [inline] do_syscall_64+0x2bd/0x3b0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f2d8a7907bc Code: Unable to access opcode bytes at 0x7f2d8a790792. RSP: 002b:00007ffcc12ddaa0 EFLAGS: 00000293 ORIG_RAX: 000000000000002c RAX: 0000000000000028 RBX: 00007f2d8b4e4620 RCX: 00007f2d8a7907bc RDX: 0000000000000028 RSI: 00007f2d8b4e4670 RDI: 0000000000000003 RBP: 0000000000000000 R08: 00007ffcc12ddaf4 R09: 000000000000000c R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000003 R13: 0000000000000000 R14: 00007f2d8b4e4670 R15: 0000000000000000