From 121fc4f9f331cc85cfc4c85c99b2cbf7ea5c53ac Mon Sep 17 00:00:00 2001 From: John Ferlan Date: Sat, 15 Nov 2014 08:09:53 -0500 Subject: [PATCH] qemu: Resolve Coverity UNINIT For some reason, commit id '72b4151f' triggered a Coverity uninitialized 'reply' variable check when referenced within the for loop. It seems Coverity doesn't know that flags will have to be either AFFECT_LIVE or AFFECT_CONFIG after the virDomainLiveConfigHelperMethod call. By adding a "sa_assert()" to confirm that fact, Coverity is happy again. --- src/qemu/qemu_driver.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c index 9b19629a02..a84fd479e7 100644 --- a/src/qemu/qemu_driver.c +++ b/src/qemu/qemu_driver.c @@ -17000,6 +17000,8 @@ qemuDomainGetBlockIoTune(virDomainPtr dom, if (virDomainLiveConfigHelperMethod(caps, driver->xmlopt, vm, &flags, &persistentDef) < 0) goto endjob; + sa_assert((flags & VIR_DOMAIN_AFFECT_LIVE) || + (flags & VIR_DOMAIN_AFFECT_CONFIG)); if (flags & VIR_DOMAIN_AFFECT_LIVE) { /* If the VM is running, we can check if the current VM can use -- 2.47.2