============================================
WARNING: possible recursive locking detected
6.3.0-rc6-syzkaller-gde4664485abb #0 Not tainted
--------------------------------------------
syz-executor.0/5544 is trying to acquire lock:
ffffffff8d7ae7b8 (qp_broker_list.mutex){+.+.}-{3:3}, at: vmci_qp_broker_detach+0xf5/0x1210 drivers/misc/vmw_vmci/vmci_queue_pair.c:2095

but task is already holding lock:
ffffffff8d7ae7b8 (qp_broker_list.mutex){+.+.}-{3:3}, at: vmci_qp_broker_detach+0xf5/0x1210 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-executor.0/5544:
 #0: ffffffff8d7ae7b8 (qp_broker_list.mutex){+.+.}-{3:3}, at: vmci_qp_broker_detach+0xf5/0x1210 drivers/misc/vmw_vmci/vmci_queue_pair.c:2095

stack backtrace:
CPU: 1 PID: 5544 Comm: syz-executor.0 Not tainted 6.3.0-rc6-syzkaller-gde4664485abb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 print_deadlock_bug kernel/locking/lockdep.c:2991 [inline]
 check_deadlock kernel/locking/lockdep.c:3034 [inline]
 validate_chain+0x472a/0x58e0 kernel/locking/lockdep.c:3819
 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
 lock_acquire+0x1e1/0x520 kernel/locking/lockdep.c:5669
 __mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 vmci_qp_broker_detach+0xf5/0x1210 drivers/misc/vmw_vmci/vmci_queue_pair.c:2095
 ctx_free_ctx drivers/misc/vmw_vmci/vmci_context.c:444 [inline]
 kref_put include/linux/kref.h:65 [inline]
 vmci_ctx_put+0x7d1/0xe30 drivers/misc/vmw_vmci/vmci_context.c:497
 vmci_ctx_enqueue_datagram+0x392/0x430 drivers/misc/vmw_vmci/vmci_context.c:360
 dg_dispatch_as_host drivers/misc/vmw_vmci/vmci_datagram.c:275 [inline]
 vmci_datagram_dispatch+0x441/0xbd0 drivers/misc/vmw_vmci/vmci_datagram.c:339
 qp_notify_peer drivers/misc/vmw_vmci/vmci_queue_pair.c:1481 [inline]
 vmci_qp_broker_detach+0xb58/0x1210 drivers/misc/vmw_vmci/vmci_queue_pair.c:2188
 ctx_free_ctx drivers/misc/vmw_vmci/vmci_context.c:444 [inline]
 kref_put include/linux/kref.h:65 [inline]
 vmci_ctx_put+0x7d1/0xe30 drivers/misc/vmw_vmci/vmci_context.c:497
 vmci_host_close+0x9b/0x160 drivers/misc/vmw_vmci/vmci_host.c:143
 __fput+0x3b7/0x890 fs/file_table.c:321
 task_work_run+0x24a/0x300 kernel/task_work.c:179
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
 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+0x64/0x280 kernel/entry/common.c:297
 do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f486c43bc8b
Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44
RSP: 002b:00007ffdc76af340 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007f486c43bc8b
RDX: 0000001b2c920000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007f486c59d960 R08: 0000000000000000 R09: 0000000000000010
R10: 00007ffdc7744080 R11: 0000000000000293 R12: 0000000000013618
R13: 00007ffdc76af440 R14: 00007ffdc76af460 R15: 0000000000000032
 </TASK>