On Thu, Nov 16, 2017 at 05:58:18PM +0000, Marc Zyngier wrote:
> We miss a test against NULL after allocation.
>
> Fixes: 6d03a68f8054 ("KVM: arm64: vgic-its: Turn device_id validation into
> generic ID validation")
> Cc: [email protected] # 4.8
> Reported-by: AKASHI Takahiro <[email protected]>
> Signed-off-by: Marc Zyngier <[email protected]>
> ---
> virt/kvm/arm/vgic/vgic-its.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/virt/kvm/arm/vgic/vgic-its.c b/virt/kvm/arm/vgic/vgic-its.c
> index 370086006838..30f7c7e6d2f4 100644
> --- a/virt/kvm/arm/vgic/vgic-its.c
> +++ b/virt/kvm/arm/vgic/vgic-its.c
> @@ -821,6 +821,8 @@ static int vgic_its_alloc_collection(struct vgic_its *its,
> return E_ITS_MAPC_COLLECTION_OOR;
>
> collection = kzalloc(sizeof(*collection), GFP_KERNEL);
> + if (!collection)
> + return -ENOMEM;
Our processing of this return value seems to be "shrug, something went
wrong, let's move on to the next command". Is this really a valid thing
to do if we're so much under memory pressure that we dannot allocate a
collection structure?
My question notwithstanding:
Acked-by: Christoffer Dall <[email protected]>
>
> collection->collection_id = coll_id;
> collection->target_addr = COLLECTION_NOT_MAPPED;
> --
> 2.14.2
>
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
