[PATCH v3 2/3] arm/arm64: KVM: Ensure memslots are within KVM_PHYS_SIZE

[PATCH v3 0/3] arm/arm64: KVM: Host 48-bit VA support and IPA limits · Christoffer Dall <hidden> · 2014-10-10
[PATCH v3 1/3] arm64: KVM: Implement 48 VA support for KVM EL2 and Stage-2 · Christoffer Dall <hidden> · 2014-10-10
[PATCH v3 1/3] arm64: KVM: Implement 48 VA support for KVM EL2 and Stage-2 · catalin.marinas@arm.com (Catalin Marinas) · 2014-10-10
[PATCH v3 1/3] arm64: KVM: Implement 48 VA support for KVM EL2 and Stage-2 · Marc Zyngier <hidden> · 2014-10-11
[PATCH v3 2/3] arm/arm64: KVM: Ensure memslots are within KVM_PHYS_SIZE · Christoffer Dall <hidden> · 2014-10-10
[PATCH v3 2/3] arm/arm64: KVM: Ensure memslots are within KVM_PHYS_SIZE · catalin.marinas@arm.com (Catalin Marinas) · 2014-10-10
[PATCH v3 2/3] arm/arm64: KVM: Ensure memslots are withinKVM_PHYS_SIZE · Marc Zyngier <hidden> · 2014-10-11
[PATCH v3 3/3] arm64: Allow 48-bits VA space without ARM_SMMU · Christoffer Dall <hidden> · 2014-10-10
[PATCH v3 3/3] arm64: Allow 48-bits VA space without ARM_SMMU · catalin.marinas@arm.com (Catalin Marinas) · 2014-10-10
[PATCH v3 3/3] arm64: Allow 48-bits VA space without ARM_SMMU · Christoffer Dall <hidden> · 2014-10-10

STALE4294d REVIEWED: 3 (3M)

From: catalin.marinas@arm.com (Catalin Marinas)
Date: 2014-10-10 15:09:32
Also in: kvm

On Fri, Oct 10, 2014 at 11:14:29AM +0100, Christoffer Dall wrote:

When creating or moving a memslot, make sure the IPA space is within the
addressable range of the guest.  Otherwise, user space can create too
large a memslot and KVM would try to access potentially unallocated page
table entries when inserting entries in the Stage-2 page tables.

Signed-off-by: Christoffer Dall <redacted>

Acked-by: Catalin Marinas <catalin.marinas@arm.com>

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help