summaryrefslogtreecommitdiffstats
path: root/include/xen/xen.h
diff options
context:
space:
mode:
authorAlexandru Elisei <alexandru.elisei@arm.com>2020-09-01 14:33:56 +0100
committerMarc Zyngier <maz@kernel.org>2020-09-04 10:53:48 +0100
commit7b75cd5128421c673153efb1236705696a1a9812 (patch)
treeb242c183acca16b689fec6d5b7c2b34e9e593967 /include/xen/xen.h
parent376426b1a953762b00df887e28d29e44ab4ff723 (diff)
downloadlinux-7b75cd5128421c673153efb1236705696a1a9812.tar.gz
linux-7b75cd5128421c673153efb1236705696a1a9812.tar.bz2
linux-7b75cd5128421c673153efb1236705696a1a9812.zip
KVM: arm64: Update page shift if stage 2 block mapping not supported
Commit 196f878a7ac2e (" KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory") modifies user_mem_abort() to send a SIGBUS signal when the fault IPA maps to a hwpoisoned page. Commit 1559b7583ff6 ("KVM: arm/arm64: Re-check VMA on detecting a poisoned page") changed kvm_send_hwpoison_signal() to use the page shift instead of the VMA because at that point the code had already released the mmap lock, which means userspace could have modified the VMA. If userspace uses hugetlbfs for the VM memory, user_mem_abort() tries to map the guest fault IPA using block mappings in stage 2. That is not always possible, if, for example, userspace uses dirty page logging for the VM. Update the page shift appropriately in those cases when we downgrade the stage 2 entry from a block mapping to a page. Fixes: 1559b7583ff6 ("KVM: arm/arm64: Re-check VMA on detecting a poisoned page") Signed-off-by: Alexandru Elisei <alexandru.elisei@arm.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Reviewed-by: Gavin Shan <gshan@redhat.com> Link: https://lore.kernel.org/r/20200901133357.52640-2-alexandru.elisei@arm.com
Diffstat (limited to 'include/xen/xen.h')
0 files changed, 0 insertions, 0 deletions