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
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
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
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: