conf: avoid mem leak re-allocating fake NUMA capabilities

The 'caps' object is already allocated when the fake NUMA
initialization takes place.

Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

diff --git a/src/conf/capabilities.c b/src/conf/capabilities.c
index a782d92956c2e03c3ac96db4df928b069f9c6ead..b89fa22d74afeee5a1c8b9f434cbe7e3bf83ea97 100644 (file)
--- a/src/conf/capabilities.c
+++ b/src/conf/capabilities.c
@@ -1631,9 +1631,6 @@ virCapabilitiesHostNUMAInitFake(virCapsHostNUMAPtr caps)
         }
     }
 
-    caps = g_new0(virCapsHostNUMA, 1);
-    caps->cells = g_ptr_array_new_with_free_func(
-        (GDestroyNotify)virCapabilitiesFreeHostNUMACell);
     virCapabilitiesHostNUMAAddCell(caps, 0,
                                    nodeinfo.memory,
 #ifdef __linux__