From: Jiri Denemark <jdenemar@redhat.com>
Date: Mon, 9 Mar 2015 12:12:36 +0000 (+0100)
Subject: locking: Fix flags in virLockManagerLockDaemonNew
X-Git-Tag: v1.2.13.1~55
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=a065bb0fe6032ed4a5db5112339d26dd87157c82;p=thirdparty%2Flibvirt.git

locking: Fix flags in virLockManagerLockDaemonNew

virLockManager*New APIs are never called with
VIR_LOCK_MANAGER_USES_STATE. Moreover, lockd driver does not maintain
any state that would need to be transferred during migration and thus it
should not mention VIR_LOCK_MANAGER_USES_STATE at all.

Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
(cherry picked from commit 6beb75d96dc596047aedaa9e79d81a042364626a)
---

diff --git a/src/locking/lock_driver_lockd.c b/src/locking/lock_driver_lockd.c
index 8d184fec9a..2fa4923048 100644
--- a/src/locking/lock_driver_lockd.c
+++ b/src/locking/lock_driver_lockd.c
@@ -439,7 +439,7 @@ static int virLockManagerLockDaemonNew(virLockManagerPtr lock,
     virLockManagerLockDaemonPrivatePtr priv;
     size_t i;
 
-    virCheckFlags(VIR_LOCK_MANAGER_USES_STATE, -1);
+    virCheckFlags(0, -1);
 
     if (VIR_ALLOC(priv) < 0)
         return -1;