[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2] libxl: initialise nr_dom_vcpus to fix 4a6070ea9

To: Wei Liu <wei.liu2@xxxxxxxxxx>
From: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date: Mon, 24 Oct 2016 11:36:17 +0100
Cc: Juergen Gross <jgross@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Dario Faggioli <dario.faggioli@xxxxxxxxxx>
Delivery-date: Mon, 24 Oct 2016 10:36:36 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

Wei Liu writes ("[PATCH v2] libxl: initialise nr_dom_vcpus to fix 4a6070ea9"):
> Clang complains nr_dom_vcpus may be used uninitialised after
> 4a6070ea9.
> 
> The real issue is vinfo can be NULL and nr_dom_vcpus remains
> uninitialised if previous call fails.
> 
> Initialise nr_dom_vcpus to 0 at the beginning of the loop to fix the
> issue.

Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH v2] libxl: initialise nr_dom_vcpus to fix 4a6070ea9
  - From: Wei Liu

Prev by Date: Re: [Xen-devel] [PATCH] RFC x86/hvm: Don't truncate the hvm hypercall index before range checking it
Next by Date: Re: [Xen-devel] 3.18.y missing "x86/cpu: Fix SMAP check in PVOPS environments"
Previous by thread: Re: [Xen-devel] [PATCH v2] libxl: initialise nr_dom_vcpus to fix 4a6070ea9
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.