From d229b985b504261369f2035936cc147c2606fa92 Mon Sep 17 00:00:00 2001 From: Christian Borntraeger Date: Tue, 14 Oct 2014 11:50:27 +0200 Subject: [PATCH] valgrind: avoid false positives in KVM_GET_DIRTY_LOG ioctl struct kvm_dirty_log contains padding fields that trigger false positives in valgrind. Let's use a designated initializer to avoid false positives from valgrind/memcheck. Signed-off-by: Christian Borntraeger Signed-off-by: Paolo Bonzini --- kvm-all.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kvm-all.c b/kvm-all.c index c86626f9ff..4bfecccf8e 100644 --- a/kvm-all.c +++ b/kvm-all.c @@ -417,7 +417,7 @@ static int kvm_physical_sync_dirty_bitmap(MemoryRegionSection *section) { KVMState *s = kvm_state; unsigned long size, allocated_size = 0; - KVMDirtyLog d; + KVMDirtyLog d = {}; KVMSlot *mem; int ret = 0; hwaddr start_addr = section->offset_within_address_space; -- 2.11.0