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.
---
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 code
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() would fail
