Re: [libvirt] [PATCH] parallels: Avoid possible leak of "cpu" from parallelsBuildCapabilities

2014-06-09 Thread Peter Krempa
On 06/09/14 09:43, Martin Kletzander wrote: > On Mon, Jun 09, 2014 at 09:39:44AM +0200, Peter Krempa wrote: >> 4d06af97d38c3648937eb8f732704379b3cd9e59 introduced a possible memory >> leak of the memory allocated into the "cpu" pointer in >> parallelsBuildCapabilities in the case "nodeGetInfo()" wo

Re: [libvirt] [PATCH] parallels: Avoid possible leak of "cpu" from parallelsBuildCapabilities

2014-06-09 Thread Martin Kletzander
On Mon, Jun 09, 2014 at 09:39:44AM +0200, Peter Krempa wrote: 4d06af97d38c3648937eb8f732704379b3cd9e59 introduced a possible memory leak of the memory allocated into the "cpu" pointer in parallelsBuildCapabilities in the case "nodeGetInfo()" would fail right after the allocation. Rearrange the co

[libvirt] [PATCH] parallels: Avoid possible leak of "cpu" from parallelsBuildCapabilities

2014-06-09 Thread Peter Krempa
4d06af97d38c3648937eb8f732704379b3cd9e59 introduced a possible memory leak of the memory allocated into the "cpu" pointer in parallelsBuildCapabilities in the case "nodeGetInfo()" would fail right after the allocation. Rearrange the code to avoid the possibility of the leak. Found by Coverity. ---