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

2014-10-06 Thread Christoffer Dall
On Tue, Sep 30, 2014 at 01:46:51PM +0100, Catalin Marinas wrote: On Thu, Sep 25, 2014 at 08:42:54PM +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

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

2014-10-06 Thread Catalin Marinas
On Mon, Oct 06, 2014 at 02:47:01PM +0100, Christoffer Dall wrote: On Tue, Sep 30, 2014 at 01:46:51PM +0100, Catalin Marinas wrote: On Thu, Sep 25, 2014 at 08:42:54PM +0100, Christoffer Dall wrote: When creating or moving a memslot, make sure the IPA space is within the addressable range

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

2014-09-30 Thread Catalin Marinas
On Thu, Sep 25, 2014 at 08:42:54PM +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

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

2014-09-25 Thread Christoffer Dall
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: