David Woodhouse 42a90008f8 KVM: Ensure lockdep knows about kvm->lock vs. vcpu->mutex ordering rule ...

Documentation/virt/kvm/locking.rst tells us that kvm->lock is taken outside
vcpu->mutex. But that doesn't actually happen very often; it's only in
some esoteric cases like migration with AMD SEV. This means that lockdep
usually doesn't notice, and doesn't do its job of keeping us honest.

Ensure that lockdep *always* knows about the ordering of these two locks,
by briefly taking vcpu->mutex in kvm_vm_ioctl_create_vcpu() while kvm->lock
is held.

Signed-off-by: David Woodhouse <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>

2023-01-11 13:32:21 -05:00

..

kvm

KVM: Ensure lockdep knows about kvm->lock vs. vcpu->mutex ordering rule

2023-01-11 13:32:21 -05:00

lib

Revert "irqbypass: do not start cons/prod when failed connect"

2021-05-15 10:26:55 +01:00

Makefile

…