From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58139) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y0Yfg-0005LQ-Or for qemu-devel@nongnu.org; Mon, 15 Dec 2014 11:39:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y0Yfa-00053t-Ji for qemu-devel@nongnu.org; Mon, 15 Dec 2014 11:38:56 -0500 Received: from mx1.redhat.com ([209.132.183.28]:41056) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y0Yfa-00053p-D3 for qemu-devel@nongnu.org; Mon, 15 Dec 2014 11:38:50 -0500 From: Paolo Bonzini Date: Mon, 15 Dec 2014 17:37:49 +0100 Message-Id: <1418661511-22348-6-git-send-email-pbonzini@redhat.com> In-Reply-To: <1418661511-22348-1-git-send-email-pbonzini@redhat.com> References: <1418661511-22348-1-git-send-email-pbonzini@redhat.com> Subject: [Qemu-devel] [PULL 05/47] valgrind: avoid false positives in KVM_GET_DIRTY_LOG ioctl List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Christian Borntraeger From: Christian Borntraeger 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 c86626f..4bfeccc 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; -- 1.8.3.1