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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 11 Aug 2011 16:47:35 -0400
From:	Andrew Lutomirski <luto@....edu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>, mingo@...hat.com,
	hpa@...or.com, x86@...nel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	keir.xen@...il.com, xen-devel@...ts.xensource.com,
	virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1

On Thu, Aug 11, 2011 at 4:28 PM, Jeremy Fitzhardinge <jeremy@...p.org> 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@...cle.com> 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@...nel.org 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/