diff options
| author | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2014-09-12 17:16:00 +0400 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2014-09-14 18:26:05 +0400 |
| commit | 85c8555ff07ef09261bd50d603cd4290cff5a8cc (patch) | |
| tree | 34a42659b3e0cbb905c3083b37a62d4e9594d206 /mm/memory.c | |
| parent | 0b70068e47e8f0c813a902dc3d6def601fd15acb (diff) | |
| download | linux-85c8555ff07ef09261bd50d603cd4290cff5a8cc.tar.xz | |
KVM: check for !is_zero_pfn() in kvm_is_mmio_pfn()
Read-only memory ranges may be backed by the zero page, so avoid
misidentifying it a a MMIO pfn.
This fixes another issue I identified when testing QEMU+KVM_UEFI, where
a read to an uninitialized emulated NOR flash brought in the zero page,
but mapped as a read-write device region, because kvm_is_mmio_pfn()
misidentifies it as a MMIO pfn due to its PG_reserved bit being set.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Fixes: b88657674d39 ("ARM: KVM: user_mem_abort: support stage 2 MMIO page mapping")
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'mm/memory.c')
0 files changed, 0 insertions, 0 deletions