KVM: x86: do not report preemption if the steal time cache is stale
stable inclusion from stable-v5.10.180 commit 85cfbaa575eaa843a15ab2d54b953196c2189b2f category: bugfix bugzilla: https://gitee.com/openeuler/kernel/issues/I8FC2O Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=85cfbaa575eaa843a15ab2d54b953196c2189b2f -------------------------------- From: Paolo Bonzini <pbonzini@redhat.com> commit c3c28d24 upstream. Commit 7e2175eb ("KVM: x86: Fix recording of guest steal time / preempted status", 2021-11-11) open coded the previous call to kvm_map_gfn, but in doing so it dropped the comparison between the cached guest physical address and the one in the MSR. This cause an incorrect cache hit if the guest modifies the steal time address while the memslots remain the same. This can happen with kexec, in which case the preempted bit is written at the address used by the old kernel instead of the old one. Cc: David Woodhouse <dwmw@amazon.co.uk> Cc: stable@vger.kernel.org Fixes: 7e2175eb ("KVM: x86: Fix recording of guest steal time / preempted status") Signed-off-by:Paolo Bonzini <pbonzini@redhat.com> Signed-off-by:
Rishabh Bhatnagar <risbhat@amazon.com> Tested-by:
Allen Pais <apais@linux.microsoft.com> Acked-by:
Sean Christopherson <seanjc@google.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
sanglipeng <sanglipeng1@jd.com>
Loading
Please sign in to comment