Wanpeng Li e160ee96d0 KVM: Fix lockdep false negative during host resume ... [ Upstream commit 4cb9a998b1 ] I saw the below splatting after the host suspended and resumed. WARNING: CPU: 0 PID: 2943 at kvm/arch/x86/kvm/../../../virt/kvm/kvm_main.c:5531 kvm_resume+0x2c/0x30 [kvm] CPU: 0 PID: 2943 Comm: step_after_susp Tainted: G W IOE 5.17.0-rc3+ #4 RIP: 0010:kvm_resume+0x2c/0x30 [kvm] Call Trace: <TASK> syscore_resume+0x90/0x340 suspend_devices_and_enter+0xaee/0xe90 pm_suspend.cold+0x36b/0x3c2 state_store+0x82/0xf0 kernfs_fop_write_iter+0x1b6/0x260 new_sync_write+0x258/0x370 vfs_write+0x33f/0x510 ksys_write+0xc9/0x160 do_syscall_64+0x3b/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae lockdep_is_held() can return -1 when lockdep is disabled which triggers this warning. Let's use lockdep_assert_not_held() which can detect incorrect calls while holding a lock and it also avoids false negatives when lockdep is disabled. Signed-off-by: Wanpeng Li <wanpengli@tencent.com> Message-Id: <1644920142-81249-1-git-send-email-wanpengli@tencent.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Sasha Levin <sashal@kernel.org>		2022-03-16 14:23:40 +01:00
..
async_pf.c
async_pf.h
binary_stats.c
coalesced_mmio.c
coalesced_mmio.h
dirty_ring.c
eventfd.c	KVM: eventfd: Fix false positive RCU usage warning	2022-02-16 12:56:16 +01:00
irqchip.c
Kconfig
kvm_main.c	KVM: Fix lockdep false negative during host resume	2022-03-16 14:23:40 +01:00
mmu_lock.h
vfio.c
vfio.h