From f73198df3b9ee2e3cca20e7aa7e75fe191dac7f6 Mon Sep 17 00:00:00 2001 From: Eric Blake Date: Fri, 3 Jun 2011 13:53:26 -0600 Subject: [PATCH] python: avoid unlikely sign extension bug Detected by Coverity. cpumap was allocated with a value of (unsigned short)*(int), which is an int computation, and then promotes to size_t. On a 64-bit platform, this fails if bit 32 of the product is set (because of sign extension giving a HUGE value to malloc), even though a naive programmer would assume that since the first value is unsigned, the product is also unsigned and at most 4GB would be allocated. Won't bite in practice (the product should never be that large), but worth using the right types to begin with, so that we are now computing (unsigned short)*(size_t). * python/libvirt-override.c (libvirt_virDomainGetVcpus): Use correct type. --- python/libvirt-override.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/python/libvirt-override.c b/python/libvirt-override.c index 763df0028e..974decb68c 100644 --- a/python/libvirt-override.c +++ b/python/libvirt-override.c @@ -414,7 +414,7 @@ libvirt_virDomainGetVcpus(PyObject *self ATTRIBUTE_UNUSED, virDomainInfo dominfo; virVcpuInfoPtr cpuinfo = NULL; unsigned char *cpumap = NULL; - int cpumaplen, i; + size_t cpumaplen, i; int i_retval; if (!PyArg_ParseTuple(args, (char *)"O:virDomainGetVcpus",