From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [patch v2] x86: kvm: x86: fix information leak to userland Date: Tue, 26 Jul 2011 20:24:33 +0300 Message-ID: <4E2EF851.8060202@redhat.com> References: <1288447871-7715-1-git-send-email-segooon@gmail.com> <4CCC2D11.7090109@web.de> <20101030153147.GA14169@albatros> <4CCC3DC2.6090505@web.de> <20101030185447.GA7629@albatros> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Vasiliy Kulikov , Jan Kiszka , kernel-janitors@vger.kernel.org, Marcelo Tosatti , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: Alexander Graf Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 07/26/2011 08:05 PM, Alexander Graf wrote: > struct kvm_pit_state2 { > struct kvm_pit_channel_state channels[3]; > __u32 flags; > __u32 reserved[9]; > }; > > So memset(&ps->reserved) would give you the a __u32 **, no? Same goes for all the other array sets in here. Or am I understanding some C logic wrong? :) > An address of an array is the array itself. -- error compiling committee.c: too many arguments to function