From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lutomirski Subject: Re: [PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1 Date: Thu, 11 Aug 2011 16:47:35 -0400 Message-ID: References: <20110803135322.GC29501@dumpdata.com> <20110803135604.GA29761@dumpdata.com> <4E443B52.3080609@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4E443B52.3080609@goop.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Jeremy Fitzhardinge Cc: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk , x86@kernel.org, Linux Kernel Mailing List , virtualization@lists.linux-foundation.org, keir.xen@gmail.com, hpa@zytor.com, mingo@redhat.com List-Id: virtualization@lists.linuxfoundation.org On Thu, Aug 11, 2011 at 4:28 PM, Jeremy Fitzhardinge wrot= e: > On 08/03/2011 06:59 AM, Andrew Lutomirski wrote: >> On Wed, Aug 3, 2011 at 9:56 AM, Konrad Rzeszutek Wilk >> wrote: >>> On Wed, Aug 03, 2011 at 09:53:22AM -0400, Konrad Rzeszutek Wilk wrote: >>>> On Wed, Aug 03, 2011 at 09:31:48AM -0400, Andy Lutomirski wrote: >>>>> This fixes various problems that cropped up with the vdso patches. >>>>> >>>>> =A0- Patch 1 fixes an information leak to userspace. >>>>> =A0- Patches 2 and 3 fix the kernel build on gold. >>>>> =A0- Patches 4 and 5 fix Xen (I hope). >>>>> =A0- Patch 6 (optional) adds a trace event to vsyscall emulation. =A0= It will >>>>> =A0 =A0make it easier to handle performance regression reports :) >>>> Hm, you seemed to have the x86 maintainers on your email.. >>> I definitly need some coffee. What I meant was that you missing putting >>> the x86 maintainers on this patchset. They are the ones that will handl= e this. >>> >>> I put them on the To list for you. >> Are you sure about that coffee? =A0I'm pretty sure I had x86@kernel.org = in there. > > What's the state of this series? =A0Has tip.git picked it up, or does it > need another go-around? > > I just booted a Linus tree and got a backtrace that looks like this > issue, though I haven't looked into it in detail yet. It's in tip/x86/vdso. I don't know it's status on the way from there to -l= inus. --Andy