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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110803135604.GA29761@dumpdata.com>
Date:	Wed, 3 Aug 2011 09:56:04 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Andy Lutomirski <luto@....edu>, mingo@...hat.com, hpa@...or.com,
	x86@...nel.org
Cc:	x86@...nel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	jeremy@...p.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 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.
> > 
> > [1] https://gitorious.org/linux-test-utils/linux-clock-tests
> > 
> > Changes from v1:
> >  - Improve changelog message for "x86-64/xen: Enable the vvar mapping"
> >  - Fix 32-bit build.
> >  - Add patch 6.
> > 
> > Andy Lutomirski (6):
> >   x86-64: Pad vDSO to a page boundary
> >   x86-64: Move the "user" vsyscall segment out of the data segment.
> >   x86-64: Work around gold bug 13023
> >   x86-64/xen: Enable the vvar mapping
> >   x86-64: Add user_64bit_mode paravirt op
> >   x86-64: Add vsyscall:emulate_vsyscall trace event
> > 
> >  arch/x86/include/asm/desc.h           |    4 +-
> >  arch/x86/include/asm/paravirt_types.h |    6 ++++
> >  arch/x86/include/asm/ptrace.h         |   19 +++++++++++++
> >  arch/x86/kernel/paravirt.c            |    4 +++
> >  arch/x86/kernel/step.c                |    2 +-
> >  arch/x86/kernel/vmlinux.lds.S         |   46 ++++++++++++++++++---------------
> >  arch/x86/kernel/vsyscall_64.c         |   12 +++++---
> >  arch/x86/kernel/vsyscall_trace.h      |   29 ++++++++++++++++++++
> >  arch/x86/mm/fault.c                   |    2 +-
> >  arch/x86/vdso/vdso.S                  |    1 +
> >  arch/x86/xen/enlighten.c              |    4 +++
> >  arch/x86/xen/mmu.c                    |    4 ++-
> >  12 files changed, 102 insertions(+), 31 deletions(-)
> >  create mode 100644 arch/x86/kernel/vsyscall_trace.h
> > 
> > -- 
> > 1.7.6
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ