diff options
| author | Yan Zhao <[email protected]> | 2025-03-18 01:33:10 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2025-04-28 18:03:06 +0000 |
| commit | 11d45175111d933c5175acc28e56af2213dd5cd6 (patch) | |
| tree | 954b17d4c3727c8b2a8fe35e44f69837c22e2ca7 /rust/helpers/mutex.c | |
| parent | KVM: x86/tdp_mmu: WARN if PFN changes for spurious faults (diff) | |
| download | kernel-11d45175111d933c5175acc28e56af2213dd5cd6.tar.gz kernel-11d45175111d933c5175acc28e56af2213dd5cd6.zip | |
KVM: x86/mmu: Warn if PFN changes on shadow-present SPTE in shadow MMU
Warn if PFN changes on shadow-present SPTE in mmu_set_spte().
KVM should _never_ change the PFN of a shadow-present SPTE. In
mmu_set_spte(), there is a WARN_ON_ONCE() on pfn changes on shadow-present
SPTE in mmu_spte_update() to detect this condition. However, that
WARN_ON_ONCE() is not hittable since mmu_set_spte() invokes drop_spte()
earlier before mmu_spte_update(), which clears SPTE to a !shadow-present
state. So, before invoking drop_spte(), add a WARN_ON_ONCE() in
mmu_set_spte() to warn PFN change of a shadow-present SPTE.
For the spurious prefetch fault, only return RET_PF_SPURIOUS directly when
PFN is not changed. When PFN changes, fall through to follow the sequence
of drop_spte(), warn of PFN change, make_spte(), flush tlb, rmap_add().
Signed-off-by: Yan Zhao <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'rust/helpers/mutex.c')
0 files changed, 0 insertions, 0 deletions
