From: Marcelo Tosatti <mtosatti@redhat.com>
Date: Tue, 12 May 2009 21:55:44 +0000 (-0300)
Subject: KVM: take mmu_lock when updating a deleted slot
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=b43b1901ad282aeb74161837fb403927102687a1;p=GitHub%2FLineageOS%2Fandroid_kernel_samsung_universal7580.git

KVM: take mmu_lock when updating a deleted slot

kvm_handle_hva relies on mmu_lock protection to safely access
the memslot structures.

Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
---

diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index 687d113a3e5..5fed9bfc3cf 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -1210,8 +1210,10 @@ int __kvm_set_memory_region(struct kvm *kvm,
 
 	kvm_free_physmem_slot(&old, npages ? &new : NULL);
 	/* Slot deletion case: we have to update the current slot */
+	spin_lock(&kvm->mmu_lock);
 	if (!npages)
 		*memslot = old;
+	spin_unlock(&kvm->mmu_lock);
 #ifdef CONFIG_DMAR
 	/* map the pages in iommu page table */
 	r = kvm_iommu_map_pages(kvm, base_gfn, npages);