============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.3995/24248 is trying to acquire lock:
ffffffff8f2c5bb8 (qp_broker_list.mutex){+.+.}-{4:4}, at: vmci_qp_broker_detach+0x14c/0x1380 drivers/misc/vmw_vmci/vmci_queue_pair.c:2095

but task is already holding lock:
ffffffff8f2c5bb8 (qp_broker_list.mutex){+.+.}-{4:4}, at: vmci_qp_broker_detach+0x14c/0x1380 drivers/misc/vmw_vmci/vmci_queue_pair.c:2095

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(qp_broker_list.mutex);
  lock(qp_broker_list.mutex);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

1 lock held by syz.0.3995/24248:
 #0: ffffffff8f2c5bb8 (qp_broker_list.mutex){+.+.}-{4:4}, at: vmci_qp_broker_detach+0x14c/0x1380 drivers/misc/vmw_vmci/vmci_queue_pair.c:2095

stack backtrace:
CPU: 1 UID: 0 PID: 24248 Comm: syz.0.3995 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_deadlock_bug+0x1e9/0x240 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain kernel/locking/lockdep.c:3895 [inline]
 __lock_acquire+0x1106/0x1c90 kernel/locking/lockdep.c:5237
 lock_acquire kernel/locking/lockdep.c:5868 [inline]
 lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825
 __mutex_lock_common kernel/locking/mutex.c:598 [inline]
 __mutex_lock+0x193/0x1060 kernel/locking/mutex.c:760
 vmci_qp_broker_detach+0x14c/0x1380 drivers/misc/vmw_vmci/vmci_queue_pair.c:2095
 ctx_free_ctx+0x51b/0xdb0 drivers/misc/vmw_vmci/vmci_context.c:424
 kref_put include/linux/kref.h:65 [inline]
 vmci_ctx_put drivers/misc/vmw_vmci/vmci_context.c:477 [inline]
 vmci_ctx_enqueue_datagram+0x4c5/0x650 drivers/misc/vmw_vmci/vmci_context.c:340
 dg_dispatch_as_host drivers/misc/vmw_vmci/vmci_datagram.c:276 [inline]
 vmci_datagram_dispatch+0x42e/0xd30 drivers/misc/vmw_vmci/vmci_datagram.c:340
 qp_notify_peer+0x19d/0x260 drivers/misc/vmw_vmci/vmci_queue_pair.c:1481
 vmci_qp_broker_detach+0x604/0x1380 drivers/misc/vmw_vmci/vmci_queue_pair.c:2188
 ctx_free_ctx+0x51b/0xdb0 drivers/misc/vmw_vmci/vmci_context.c:424
 kref_put include/linux/kref.h:65 [inline]
 vmci_ctx_put drivers/misc/vmw_vmci/vmci_context.c:477 [inline]
 vmci_ctx_destroy+0x15b/0x1d0 drivers/misc/vmw_vmci/vmci_context.c:195
 vmci_host_close+0x115/0x1a0 drivers/misc/vmw_vmci/vmci_host.c:143
 __fput+0x402/0xb70 fs/file_table.c:468
 task_work_run+0x150/0x240 kernel/task_work.c:227
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 exit_to_user_mode_loop+0xec/0x130 kernel/entry/common.c:43
 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
 syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline]
 do_syscall_64+0x426/0xfa0 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe81418efc9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe8150a0038 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007fe8143e6090 RCX: 00007fe81418efc9
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000000000004
RBP: 00007fe814211f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fe8143e6128 R14: 00007fe8143e6090 R15: 00007ffc052b9a28
 </TASK>