Alexandru recently reported an interesting issue with our handling
of device mapping in user_mem_abort(), which is sligtly less than
correct. The first patch of the series address this issue, and
is a stable candidate.
While I was looking at this code, I spotted what I think is a potential
issue when handling a poisoned page, where we can race with a VMA
being removed. This second patch is mostly a RFC, as this is not
my area of expertise.
Finally, the last patch is a cleanup removing an unnecessary console
output.
Marc Zyngier (3):
KVM: arm/arm64: Properly handle faulting of device mappings
KVM: arm/arm64: Re-check VMA on detecting a poisoned page
KVM: arm/arm64: Drop spurious message when faulting on a non-existent
mapping
virt/kvm/arm/mmu.c | 47 +++++++++++++++++++++++++++++++++++++++-------
1 file changed, 40 insertions(+), 7 deletions(-)
--
2.20.1
