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

[Xen-devel] [PATCH] correct indexing in xc_cpu_to_node_t map


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: beth kon <eak@xxxxxxxxxx>
  • Date: Fri, 17 Aug 2007 16:04:35 -0400
  • Delivery-date: Fri, 17 Aug 2007 13:07:24 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Looks like there is a nit with initilizing the map array. It needs one more element than MAX_CPU_ID since indexing starts at 0.

Signed-off-by: Beth Kon <eak@xxxxxxxxxx>

diff -r 256160ff19b7 tools/python/xen/lowlevel/xc/xc.c
--- a/tools/python/xen/lowlevel/xc/xc.c Thu Aug 16 13:27:59 2007 +0100
+++ b/tools/python/xen/lowlevel/xc/xc.c Fri Aug 17 15:44:22 2007 -0400
@@ -685,7 +685,7 @@ static PyObject *pyxc_physinfo(XcObject
    char cpu_cap[128], *p=cpu_cap, *q=cpu_cap;
    int i, j, max_cpu_id;
    PyObject *ret_obj, *node_to_cpu_obj;
-    xc_cpu_to_node_t map[MAX_CPU_ID];
+    xc_cpu_to_node_t map[MAX_CPU_ID + 1];

    set_xen_guest_handle(info.cpu_to_node, map);
    info.max_cpu_id = MAX_CPU_ID;

--
Elizabeth Kon (Beth)
IBM Linux Technology Center
Open Hypervisor Team
email: eak@xxxxxxxxxx


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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