From: Daniel P. Berrange <berrange@redhat.com>
Date: Wed, 25 Sep 2013 14:17:51 +0000 (+0100)
Subject: Fix leak in virLockSpaceResourceFree
X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=06bfe6fe2b6396c48d1c98eaea409d15ac9f7bb7;p=libvirt.git

Fix leak in virLockSpaceResourceFree

Normally a lockspace resource is not freed while there are
active owners. During initial resource creation though, an
OOM error will trigger this scenario. virLockSpaceResourceFree
was not freeing the 'owners' field in this case.

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
---

diff --git a/src/util/virlockspace.c b/src/util/virlockspace.c
index afb1abbbbb..cab7775c7a 100644
--- a/src/util/virlockspace.c
+++ b/src/util/virlockspace.c
@@ -102,6 +102,7 @@ static void virLockSpaceResourceFree(virLockSpaceResourcePtr res)
         }
     }
 
+    VIR_FREE(res->owners);
     VIR_FORCE_CLOSE(res->fd);
     VIR_FREE(res->path);
     VIR_FREE(res->name);