Skip to content

KVM: arm/arm64: user_mem_abort() assorted fixes

Marc Zyngier kvm kvmarm linux-arm-kernel stable 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 15 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3KVM: arm/arm64: Properly handle faulting of device mappingsvirt/kvm/arm/mmu.c+17 -48 replies
2/3KVM: arm/arm64: Re-check VMA on detecting a poisoned pagevirt/kvm/arm/mmu.c+23 -26 replies
3/3KVM: arm/arm64: Drop spurious message when faulting on a non-existent mappingvirt/kvm/arm/mmu.c+0 -11 reply

Reviews trailers per patch

2 of 3 patches have a Reviewed-by or Acked-by.

PatchAlexandru EliseiJames MorseChristoffer Dall
1/3T-b R-b
2/3
3/3A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.

Read the v1 thread

Cover letter [PATCH 0/3] KVM: arm/arm64: user_mem_abort() assorted fixes

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(-)
Signature · 1 line
2.20.1