From: Peter Krempa <[email protected]>

Add debug statement when adding a lockspace in the daemon and log the
pointer when creating a new lockspace so that it can be inferred from
the log what parameters were used.

Signed-off-by: Peter Krempa <[email protected]>
---
 src/locking/lock_daemon.c | 3 +++
 src/util/virlockspace.c   | 6 ++----
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/src/locking/lock_daemon.c b/src/locking/lock_daemon.c
index 1017fc65b1..2cb7e85b39 100644
--- a/src/locking/lock_daemon.c
+++ b/src/locking/lock_daemon.c
@@ -280,6 +280,9 @@ int virLockDaemonAddLockSpace(virLockDaemon *lockd,
                               virLockSpace *lockspace)
 {
     int ret;
+
+    VIR_DEBUG("path='%s' lockspace='%p'", NULLSTR(path), lockspace);
+
     virLockDaemonLock(lockd);
     ret = virHashAddEntry(lockd->lockspaces, path, lockspace);
     virLockDaemonUnlock(lockd);
diff --git a/src/util/virlockspace.c b/src/util/virlockspace.c
index 19aacf61bc..d3c95840b3 100644
--- a/src/util/virlockspace.c
+++ b/src/util/virlockspace.c
@@ -231,11 +231,9 @@ static void virLockSpaceResourceDataFree(void *opaque)

 virLockSpace *virLockSpaceNew(const char *directory)
 {
-    virLockSpace *lockspace;
-
-    VIR_DEBUG("directory=%s", NULLSTR(directory));
+    virLockSpace *lockspace = g_new0(virLockSpace, 1);

-    lockspace = g_new0(virLockSpace, 1);
+    VIR_DEBUG("lockspace=%p directory='%s'", lockspace, NULLSTR(directory));

     if (virMutexInit(&lockspace->lock) < 0) {
         virReportError(VIR_ERR_INTERNAL_ERROR, "%s",
-- 
2.54.0

Reply via email to