linux-kernel - Re: [PATCH v2 0/4] vDSO fixes, on top of tip/x86/vdso

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: <1393572804.1019.14.camel@wall-e.seibold.net>
Date:	Fri, 28 Feb 2014 08:33:24 +0100
From:	Stefani Seibold <stefani@...bold.net>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	X86 ML <x86@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Andi Kleen <ak@...ux.intel.com>,
	Andrea Arcangeli <aarcange@...hat.com>,
	John Stultz <john.stultz@...aro.org>,
	Pavel Emelyanov <xemul@...allels.com>,
	Cyrill Gorcunov <gorcunov@...nvz.org>,
	andriy.shevchenko@...ux.intel.com, Martin.Runge@...de-schwarz.com,
	Andreas.Brief@...de-schwarz.com
Subject: Re: [PATCH v2 0/4] vDSO fixes, on top of tip/x86/vdso

Am Donnerstag, den 27.02.2014, 16:18 -0800 schrieb Andy Lutomirski:
> I'd still like someone else to confirm that the 32-bit vDSO is working
> on all common configurations before I'm happy with it, but this should
> be a considerable improvement.
> 
> Someone who maintains the clock code should review the changes in:
> 
>     commit 0fc8a237cbe98a06962f5ea37d24fc2369e23c74
>     Author: Stefani Seibold <stefani@...bold.net>
>     Date:   Wed Feb 19 10:09:10 2014 +0100
>     
>         x86, vdso: Add 32-bit VDSO time support for the 64-bit kernel
> 
> very carefully.
> 
> There's still something extremely questionable about VDSO_PAGES in the
> 32-bit vDSO code.  It appears to be terminally screwed up, and AFAICS it
> only works at all because none of the 32-bit vDSO images ever exceed
> 4096 bytes.
> 

The 4096 bytes limit was not introduced by the patch set. It is still
there for compatibility reason.
 
> Note: Patch 4 fixes a bug that's present even in -linus, so it might
> make sense to send it to Linus more quickly than the rest of this
> series.
> 
> Changes from v1:
>  - Adjust CFLAGS instead of using asmlinkage.
>  - Add more fixes.
> 
> Andy Lutomirski (4):
>   x86: Use the default ABI for the 32-bit vDSO
>   x86: Inline the CLOCK_MONOTONIC vdso code
>   x86: Patch alternatives in the 32-bit vDSO
>   x86: Zero-pad the VVAR page
> 
>  arch/x86/include/asm/vdso.h    |  2 ++
>  arch/x86/kernel/vmlinux.lds.S  |  5 +++++
>  arch/x86/vdso/Makefile         |  2 +-
>  arch/x86/vdso/vclock_gettime.c |  2 +-
>  arch/x86/vdso/vdso32-setup.c   | 25 +++++++++++++------------
>  arch/x86/vdso/vma.c            |  9 ++++++---
>  6 files changed, 28 insertions(+), 17 deletions(-)
> 


--
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/