From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36449) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SXRtk-0004b4-AS for qemu-devel@nongnu.org; Thu, 24 May 2012 02:51:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SXRtf-0005Nj-Hf for qemu-devel@nongnu.org; Thu, 24 May 2012 02:51:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54683) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SXRtf-0005NK-9k for qemu-devel@nongnu.org; Thu, 24 May 2012 02:51:43 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4O6pfTk023659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 24 May 2012 02:51:41 -0400 Received: from rincewind.home.kraxel.org (ovpn-116-33.ams2.redhat.com [10.36.116.33]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q4O6peGT012619 for ; Thu, 24 May 2012 02:51:41 -0400 Message-ID: <4FBDDA7C.2010200@redhat.com> Date: Thu, 24 May 2012 08:51:40 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <1337700600-23870-1-git-send-email-alevy@redhat.com> <4FBD338A.7050105@redhat.com> <20120524064347.GI6105@garlic.tlv.redhat.com> In-Reply-To: <20120524064347.GI6105@garlic.tlv.redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCHv2 1/3] ui/spice-display.c: add missing initialization for valgrind List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 05/24/12 08:43, Alon Levy wrote: > On Wed, May 23, 2012 at 08:59:22PM +0200, Gerd Hoffmann wrote: >> On 05/22/12 17:29, Alon Levy wrote: >>> We can't initialize QXLDevSurfaceCreate field by field because it has a >>> pa hole, and so 4 bytes remain uninitialized when building on x86-64, so >>> just memset. >> >> So you get valgrind warnings for the hole? why? nobody should ever >> access the hole, so the missing initialization should not hurt in theory ... > > Because we allocate this struct on the stack and then copy it over an fd > to spice, through the dispatcher pipe. Ah, yea, copying will make valgrind complain of course ... I'll go queue it up. cheers, Gerd