syzbot

======================================================
WARNING: possible circular locking dependency detected
6.1.28-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.1/18788 is trying to acquire lock:
ffff88802129ca00 ((work_completion)(&(&hdev->discov_off)->work)){+.+.}-{0:0}, at: __flush_work+0xcf/0x1a0 kernel/workqueue.c:3069

but task is already holding lock:
ffff88802129c078 (&hdev->lock){+.+.}-{3:3}, at: hci_unregister_dev+0x293/0x470 net/bluetooth/hci_core.c:2707

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&hdev->lock){+.+.}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
       __mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
       discov_off+0x8e/0x1f0 net/bluetooth/mgmt.c:1037
       process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
       worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
       kthread+0x26e/0x300 kernel/kthread.c:376
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

-> #0 ((work_completion)(&(&hdev->discov_off)->work)){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3098 [inline]
       check_prevs_add kernel/locking/lockdep.c:3217 [inline]
       validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832
       __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
       __flush_work+0xeb/0x1a0 kernel/workqueue.c:3069
       __cancel_work_timer+0x519/0x6a0 kernel/workqueue.c:3160
       mgmt_index_removed+0x2f6/0x440 net/bluetooth/mgmt.c:9428
       hci_unregister_dev+0x29b/0x470 net/bluetooth/hci_core.c:2708
       vhci_release+0x7f/0xd0 drivers/bluetooth/hci_vhci.c:568
       __fput+0x3b7/0x890 fs/file_table.c:320
       task_work_run+0x246/0x300 kernel/task_work.c:179
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0x6fb/0x2300 kernel/exit.c:869
       do_group_exit+0x202/0x2b0 kernel/exit.c:1019
       get_signal+0x16f7/0x17d0 kernel/signal.c:2858
       arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:869
       exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:168
       exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
       __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
       syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
       do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&hdev->lock);
                               lock((work_completion)(&(&hdev->discov_off)->work));
                               lock(&hdev->lock);
  lock((work_completion)(&(&hdev->discov_off)->work));

 *** DEADLOCK ***

1 lock held by syz-executor.1/18788:
 #0: ffff88802129c078 (&hdev->lock){+.+.}-{3:3}, at: hci_unregister_dev+0x293/0x470 net/bluetooth/hci_core.c:2707

stack backtrace:
CPU: 1 PID: 18788 Comm: syz-executor.1 Not tainted 6.1.28-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2178
 check_prev_add kernel/locking/lockdep.c:3098 [inline]
 check_prevs_add kernel/locking/lockdep.c:3217 [inline]
 validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832
 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
 __flush_work+0xeb/0x1a0 kernel/workqueue.c:3069
 __cancel_work_timer+0x519/0x6a0 kernel/workqueue.c:3160
 mgmt_index_removed+0x2f6/0x440 net/bluetooth/mgmt.c:9428
 hci_unregister_dev+0x29b/0x470 net/bluetooth/hci_core.c:2708
 vhci_release+0x7f/0xd0 drivers/bluetooth/hci_vhci.c:568
 __fput+0x3b7/0x890 fs/file_table.c:320
 task_work_run+0x246/0x300 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x6fb/0x2300 kernel/exit.c:869
 do_group_exit+0x202/0x2b0 kernel/exit.c:1019
 get_signal+0x16f7/0x17d0 kernel/signal.c:2858
 arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:869
 exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:168
 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
 syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
 do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc17d4b0e91
Code: Unable to access opcode bytes at 0x7fc17d4b0e67.
RSP: 002b:00007fc17e1a8fd0 EFLAGS: 00000293 ORIG_RAX: 00000000000000e6
RAX: fffffffffffffdfc RBX: 00007fc17d5ac120 RCX: 00007fc17d4b0e91
RDX: 00007fc17e1a9010 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007fc17d4e7ca1 R08: 0000000000000000 R09: 0000000000000058
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000058
R13: 00007fffce46c4ef R14: 00007fc17e1a9300 R15: 0000000000022000
 </TASK>