====================================================== WARNING: possible circular locking dependency detected 6.7.0-rc6-syzkaller-00078-ga4aebe936554 #0 Not tainted ------------------------------------------------------ syz-executor.4/3648 is trying to acquire lock: ffff888020804e10 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: __flush_work+0xe9/0xad0 kernel/workqueue.c:3400 but task is already holding lock: ffff888020805108 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:552 [inline] ffff888020805108 (&hdev->req_lock){+.+.}-{3:3}, at: hci_rfkill_set_block+0x12d/0x210 net/bluetooth/hci_core.c:956 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&hdev->req_lock){+.+.}-{3:3}: lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747 hci_dev_do_close net/bluetooth/hci_core.c:552 [inline] hci_rfkill_set_block+0x12d/0x210 net/bluetooth/hci_core.c:956 rfkill_set_block+0x1e7/0x430 net/rfkill/core.c:346 rfkill_fop_write+0x5bb/0x790 net/rfkill/core.c:1305 vfs_write+0x290/0xb20 fs/read_write.c:582 ksys_write+0x1a0/0x2c0 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x45/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b -> #2 (rfkill_global_mutex){+.+.}-{3:3}: lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747 rfkill_register+0x34/0x8c0 net/rfkill/core.c:1075 hci_register_dev+0x4e3/0xa40 net/bluetooth/hci_core.c:2658 __vhci_create_device drivers/bluetooth/hci_vhci.c:437 [inline] vhci_create_device+0x3ba/0x720 drivers/bluetooth/hci_vhci.c:478 vhci_get_user drivers/bluetooth/hci_vhci.c:535 [inline] vhci_write+0x3c7/0x480 drivers/bluetooth/hci_vhci.c:615 call_write_iter include/linux/fs.h:2020 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x792/0xb20 fs/read_write.c:584 ksys_write+0x1a0/0x2c0 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x45/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b -> #1 (&data->open_mutex){+.+.}-{3:3}: lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747 vhci_send_frame+0x8e/0xf0 drivers/bluetooth/hci_vhci.c:78 hci_send_frame+0x1ef/0x370 net/bluetooth/hci_core.c:3042 hci_sched_acl_pkt net/bluetooth/hci_core.c:3654 [inline] hci_sched_acl net/bluetooth/hci_core.c:3739 [inline] hci_tx_work+0xed4/0x1ef0 net/bluetooth/hci_core.c:3838 process_one_work kernel/workqueue.c:2627 [inline] process_scheduled_works+0x90f/0x1420 kernel/workqueue.c:2700 worker_thread+0xa5f/0x1000 kernel/workqueue.c:2781 kthread+0x2d3/0x370 kernel/kthread.c:388 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242 -> #0 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain+0x1909/0x5ab0 kernel/locking/lockdep.c:3869 __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137 lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 __flush_work+0x102/0xad0 kernel/workqueue.c:3400 hci_dev_close_sync+0x237/0xfe0 net/bluetooth/hci_sync.c:4982 hci_dev_do_close net/bluetooth/hci_core.c:554 [inline] hci_rfkill_set_block+0x135/0x210 net/bluetooth/hci_core.c:956 rfkill_set_block+0x1e7/0x430 net/rfkill/core.c:346 rfkill_fop_write+0x5bb/0x790 net/rfkill/core.c:1305 vfs_write+0x290/0xb20 fs/read_write.c:582 ksys_write+0x1a0/0x2c0 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x45/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b other info that might help us debug this: Chain exists of: (work_completion)(&hdev->tx_work) --> rfkill_global_mutex --> &hdev->req_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&hdev->req_lock); lock(rfkill_global_mutex); lock(&hdev->req_lock); lock((work_completion)(&hdev->tx_work)); *** DEADLOCK *** 2 locks held by syz-executor.4/3648: #0: ffffffff8ee02f28 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x1a9/0x790 net/rfkill/core.c:1297 #1: ffff888020805108 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:552 [inline] #1: ffff888020805108 (&hdev->req_lock){+.+.}-{3:3}, at: hci_rfkill_set_block+0x12d/0x210 net/bluetooth/hci_core.c:956 stack backtrace: CPU: 0 PID: 3648 Comm: syz-executor.4 Not tainted 6.7.0-rc6-syzkaller-00078-ga4aebe936554 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 check_noncircular+0x366/0x490 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain+0x1909/0x5ab0 kernel/locking/lockdep.c:3869 __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137 lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 __flush_work+0x102/0xad0 kernel/workqueue.c:3400 hci_dev_close_sync+0x237/0xfe0 net/bluetooth/hci_sync.c:4982 hci_dev_do_close net/bluetooth/hci_core.c:554 [inline] hci_rfkill_set_block+0x135/0x210 net/bluetooth/hci_core.c:956 rfkill_set_block+0x1e7/0x430 net/rfkill/core.c:346 rfkill_fop_write+0x5bb/0x790 net/rfkill/core.c:1305 vfs_write+0x290/0xb20 fs/read_write.c:582 ksys_write+0x1a0/0x2c0 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x45/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7f3ab067cce9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f3ab13370c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f3ab079bf80 RCX: 00007f3ab067cce9 RDX: 0000000000000008 RSI: 0000000020000040 RDI: 0000000000000003 RBP: 00007f3ab06c947a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f3ab079bf80 R15: 00007fff116f5418