The NOP drivers needs implementation, although the function
bodies are empty. This is because the virLockManager APIs check
for driver implementation and returns an error if there's none.
Signed-off-by: Michal Privoznik <mpriv...@redhat.com>
---
src/locking/lock_driver_nop.c | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/src/locking/lock_driver_nop.c b/src/locking/lock_driver_nop.c
index 93a988e..edb450b 100644
--- a/src/locking/lock_driver_nop.c
+++ b/src/locking/lock_driver_nop.c
@@ -101,6 +101,25 @@ static void virLockManagerNopFree(virLockManagerPtr lock
ATTRIBUTE_UNUSED)
{
}
+static int
+virLockManagerNopRememberSeclabel(virLockManagerPtr lock ATTRIBUTE_UNUSED,
+ const char *path ATTRIBUTE_UNUSED,
+ const char *model ATTRIBUTE_UNUSED,
+ const char *seclabel ATTRIBUTE_UNUSED)
+{
+ return 0;
+}
+
+static int
+virLockManagerNopRecallSeclabel(virLockManagerPtr lock ATTRIBUTE_UNUSED,
+ const char *path ATTRIBUTE_UNUSED,
+ const char *model ATTRIBUTE_UNUSED,
+ char **seclabel ATTRIBUTE_UNUSED)
+{
+ /* A positive return value means no seclabel restoring. */
+ return 1;
+}
+
virLockDriver virLockDriverNop =
{
.version = VIR_LOCK_MANAGER_VERSION,
@@ -118,4 +137,7 @@ virLockDriver virLockDriverNop =
.drvRelease = virLockManagerNopRelease,
.drvInquire = virLockManagerNopInquire,
+
+ .drvRemember = virLockManagerNopRememberSeclabel,
+ .drvRecall = virLockManagerNopRecallSeclabel,
};
--
1.8.5.5
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
