From 6d0a3a1730efdc0b0c179e5bee64749ef5eed967 Mon Sep 17 00:00:00 2001 Message-Id: <6d0a3a1730efdc0b0c179e5bee64749ef5eed967@dist-git> From: Peter Krempa Date: Thu, 2 Apr 2015 11:27:57 +0200 Subject: [PATCH] qemu: processBlockJob: Don't unlock @vm twice https://bugzilla.redhat.com/show_bug.cgi?id=1208021 Commit 1a92c719 (known as 12fdae1ebb74 downstream) moved code to handle block job events to a different function that is executed in a separate thread. The caller of processBlockJob handles locking and unlocking of @vm, so the we should not do it in the function itself. (cherry picked from commit 6b6c4ab8a6d2096bd5f50d2ae9b0a929fbaaf076) Signed-off-by: Jiri Denemark --- src/qemu/qemu_driver.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c index 4293817..0939223 100644 --- a/src/qemu/qemu_driver.c +++ b/src/qemu/qemu_driver.c @@ -4523,7 +4523,6 @@ processBlockJobEvent(virQEMUDriverPtr driver, VIR_WARN("Unable to update persistent definition on vm %s " "after block job", vm->def->name); } - virObjectUnlock(vm); virObjectUnref(cfg); if (event) -- 2.3.5