Re: [PATCH v2] KVM: arm64: its: Fix missing dynamic allocation check in scan_its_table

2017-10-13 Thread Christoffer Dall
On Fri, Oct 13, 2017 at 04:00:18PM +0200, Andrew Jones wrote: > On Fri, Oct 13, 2017 at 03:17:34PM +0200, Christoffer Dall wrote: > > We currently allocate an entry dynamically, but we never check if the > > allocation actually succeeded. We actually don't need a dynamic > > allocation, because

Re: [PATCH v2] KVM: arm64: its: Fix missing dynamic allocation check in scan_its_table

2017-10-13 Thread Andrew Jones
On Fri, Oct 13, 2017 at 03:17:34PM +0200, Christoffer Dall wrote: > We currently allocate an entry dynamically, but we never check if the > allocation actually succeeded. We actually don't need a dynamic > allocation, because we know the maximum size of an ITS table entry, so > we can simply use

Re: [PATCH v2] KVM: arm64: its: Fix missing dynamic allocation check in scan_its_table

2017-10-13 Thread Marc Zyngier
On 13/10/17 14:17, Christoffer Dall wrote: > We currently allocate an entry dynamically, but we never check if the > allocation actually succeeded. We actually don't need a dynamic > allocation, because we know the maximum size of an ITS table entry, so > we can simply use an allocation on the

[PATCH v2] KVM: arm64: its: Fix missing dynamic allocation check in scan_its_table

2017-10-13 Thread Christoffer Dall
We currently allocate an entry dynamically, but we never check if the allocation actually succeeded. We actually don't need a dynamic allocation, because we know the maximum size of an ITS table entry, so we can simply use an allocation on the stack. Cc: Signed-off-by: