[PATCH v1 03/31] testNetworkUpdate: Unlock network at the end

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Silly this bug went unnoticed so long. At the beginning we try to
find the passed network in the list of network objects. If found,
it's locked and real work takes place. Then, in the end, the
network object is never unlocked.

Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>
---
 src/test/test_driver.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/test/test_driver.c b/src/test/test_driver.c
index a386270..2bed3f2 100644
--- a/src/test/test_driver.c
+++ b/src/test/test_driver.c
@@ -3835,6 +3835,8 @@ testNetworkUpdate(virNetworkPtr net,
 
     ret = 0;
  cleanup:
+    if (network)
+        virNetworkObjUnlock(network);
     testDriverUnlock(privconn);
     return ret;
 }
-- 
2.0.5

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]