WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: [PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1
From: Andrew Lutomirski <luto@xxxxxxx>
Date: Thu, 11 Aug 2011 16:47:35 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, x86@xxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, keir.xen@xxxxxxxxx, hpa@xxxxxxxxx, mingo@xxxxxxxxxx
Delivery-date: Thu, 11 Aug 2011 13:48:47 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=qQDYjBs8s1uWeekBQuE+SvTduWeCoDpWseZvyttGpVU=; b=v6REr4fuJyKzABr9uwvj3SYqTOKekUrMmTHoa8eh2IXUo3rVzny0QIoGfIBdqz3jQ8 Imqz/xu0rO7Aqa53+MPZBDw7+bJD/4C8CGmnZuRbZPmBEEb3bipj/OPxDuZTxLC1SOtZ 0MMwfyLz0i1pCubniDNNvJh20NEj2FpIfzE8Q=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E443B52.3080609@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <cover.1312378163.git.luto@xxxxxxx> <20110803135322.GC29501@xxxxxxxxxxxx> <20110803135604.GA29761@xxxxxxxxxxxx> <CAObL_7FavQH29CENHptZphDDv7ja2P9MVM5Uj47G68ccDumBBg@xxxxxxxxxxxxxx> <4E443B52.3080609@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Aug 11, 2011 at 4:28 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> On 08/03/2011 06:59 AM, Andrew Lutomirski wrote:
>> On Wed, Aug 3, 2011 at 9:56 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@xxxxxxxxxx> 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.
>>>>>
>>>>>  - Patch 1 fixes an information leak to userspace.
>>>>>  - Patches 2 and 3 fix the kernel build on gold.
>>>>>  - Patches 4 and 5 fix Xen (I hope).
>>>>>  - Patch 6 (optional) adds a trace event to vsyscall emulation.  It will
>>>>>    make 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 handle 
>>> this.
>>>
>>> I put them on the To list for you.
>> Are you sure about that coffee?  I'm pretty sure I had x86@xxxxxxxxxx in 
>> there.
>
> What's the state of this series?  Has 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 -linus.

--Andy

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel