============================================
WARNING: possible recursive locking detected
6.1.0-rc3-syzkaller #0 Not tainted
--------------------------------------------
syz-executor385/8289 is trying to acquire lock:
ffffffff8bad8778 (qp_broker_list.mutex){+.+.}-{3:3}, at: vmci_qp_broker_detach+0x11a/0x13a0 drivers/misc/vmw_vmci/vmci_queue_pair.c:2093

but task is already holding lock:
ffffffff8bad8778 (qp_broker_list.mutex){+.+.}-{3:3}, at: vmci_qp_broker_detach+0x11a/0x13a0 drivers/misc/vmw_vmci/vmci_queue_pair.c:2093

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-executor385/8289:
 #0: ffffffff8bad8778 (qp_broker_list.mutex){+.+.}-{3:3}, at: vmci_qp_broker_detach+0x11a/0x13a0 drivers/misc/vmw_vmci/vmci_queue_pair.c:2093

stack backtrace:
CPU: 1 PID: 8289 Comm: syz-executor385 Not tainted 6.1.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x57/0x7d lib/dump_stack.c:106
 print_deadlock_bug kernel/locking/lockdep.c:2990 [inline]
 check_deadlock kernel/locking/lockdep.c:3033 [inline]
 validate_chain kernel/locking/lockdep.c:3818 [inline]
 __lock_acquire.cold+0x116/0x3a7 kernel/locking/lockdep.c:5055
 lock_acquire kernel/locking/lockdep.c:5668 [inline]
 lock_acquire+0x1df/0x630 kernel/locking/lockdep.c:5633
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
 vmci_qp_broker_detach+0x11a/0x13a0 drivers/misc/vmw_vmci/vmci_queue_pair.c:2093
 ctx_free_ctx+0x410/0xc10 drivers/misc/vmw_vmci/vmci_context.c:444
 kref_put include/linux/kref.h:65 [inline]
 vmci_ctx_put drivers/misc/vmw_vmci/vmci_context.c:497 [inline]
 vmci_ctx_enqueue_datagram+0x3de/0x530 drivers/misc/vmw_vmci/vmci_context.c:360
 dg_dispatch_as_host drivers/misc/vmw_vmci/vmci_datagram.c:275 [inline]
 vmci_datagram_dispatch+0x270/0x8b0 drivers/misc/vmw_vmci/vmci_datagram.c:339
 qp_notify_peer+0x136/0x200 drivers/misc/vmw_vmci/vmci_queue_pair.c:1479
 vmci_qp_broker_detach+0x85f/0x13a0 drivers/misc/vmw_vmci/vmci_queue_pair.c:2186
 ctx_free_ctx+0x410/0xc10 drivers/misc/vmw_vmci/vmci_context.c:444
 vmci_host_close+0xf2/0x180 drivers/misc/vmw_vmci/vmci_host.c:143
 __fput+0x1fa/0x9a0 fs/file_table.c:320
 task_work_run+0x12b/0x220 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x99f/0x2470 kernel/exit.c:820
 do_group_exit+0xb0/0x250 kernel/exit.c:950
 get_signal+0x1c31/0x1e80 kernel/signal.c:2858
 arch_do_signal_or_restart+0x88/0x1b00 arch/x86/kernel/signal.c:869
 exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
 exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:203
 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
 syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:296
 do_syscall_64+0x42/0x80 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7efd62462a19
Code: Unable to access opcode bytes at 0x7efd624629ef.
RSP: 002b:00007efd62414308 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 00007efd624ea3e8 RCX: 00007efd62462a19
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007efd624ea3ec
RBP: 00007efd624ea3e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007efd624ea3ec
R13: 00007efd624b8064 R14: 636d762f7665642f R15: 0000000000022000
 </TASK>