diff options
| author | Alexandru Elisei <alexandru.elisei@arm.com> | 2020-09-01 15:33:56 +0200 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2020-09-04 11:53:48 +0200 |
| commit | 7b75cd5128421c673153efb1236705696a1a9812 (patch) | |
| tree | b242c183acca16b689fec6d5b7c2b34e9e593967 /virt | |
| parent | KVM: arm64: Fix address truncation in traces (diff) | |
| download | linux-7b75cd5128421c673153efb1236705696a1a9812.tar.xz 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 'virt')
0 files changed, 0 insertions, 0 deletions