diff options
author | Andre Przywara <andre.przywara@arm.com> | 2018-05-11 15:20:15 +0100 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2018-05-15 13:36:53 +0200 |
commit | 711702b57cc3c50b84bd648de0f1ca0a378805be (patch) | |
tree | bc600ebc3131f613ff676175ec921bd8e7da7751 /security | |
parent | bf308242ab98b5d1648c3663e753556bef9bec01 (diff) | |
download | linux-711702b57cc3c50b84bd648de0f1ca0a378805be.tar.bz2 |
KVM: arm/arm64: VGIC/ITS save/restore: protect kvm_read_guest() calls
kvm_read_guest() will eventually look up in kvm_memslots(), which requires
either to hold the kvm->slots_lock or to be inside a kvm->srcu critical
section.
In contrast to x86 and s390 we don't take the SRCU lock on every guest
exit, so we have to do it individually for each kvm_read_guest() call.
Use the newly introduced wrapper for that.
Cc: Stable <stable@vger.kernel.org> # 4.12+
Reported-by: Jan Glauber <jan.glauber@caviumnetworks.com>
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Acked-by: Christoffer Dall <christoffer.dall@arm.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions