diff options
| author |   David Woodhouse <dwmw@amazon.co.uk> | 2023-01-11 18:06:50 +0000 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2023-01-11 13:32:21 -0500 |
| commit | 42a90008f890afc41837dfeec1f0b1e7bcecf94a (patch) | |
| tree | 52d9bef1911c441968650403c0a4519513e9781e /scripts/generate_rust_analyzer.py | |
| parent | KVM: x86/xen: Fix potential deadlock in kvm_xen_update_runstate_guest() (diff) | |
| download | wireguard-linux-42a90008f890afc41837dfeec1f0b1e7bcecf94a.tar.xz wireguard-linux-42a90008f890afc41837dfeec1f0b1e7bcecf94a.zip | |
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 <dwmw@amazon.co.uk>
Message-Id: <20230111180651.14394-3-dwmw2@infradead.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions