linux-kernel - Re: New vsyscall emulation breaks JITs

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: <20110805205222.GK5782@one.firstfloor.org>
Date:	Fri, 5 Aug 2011 22:52:22 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Andrew Lutomirski <luto@....edu>, Andi Kleen <andi@...stfloor.org>,
	x86@...nel.org, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, lueckintel@...oo.com,
	kimwooyoung@...il.com
Subject: Re: New vsyscall emulation breaks JITs

On Fri, Aug 05, 2011 at 01:48:28PM -0700, H. Peter Anvin wrote:
> On 08/05/2011 01:45 PM, Andrew Lutomirski wrote:
> > 
> > hpa: time is supported (as of 3.0) by the vdso, and very new glibc
> > uses the vdso version.  We could add a native time implementation back
> > to the vsyscall page without too much pain as a short-term fix, but
> > that would be less than ideal.
> > 
> 
> How new does glibc have to be?

Mine from May 17 doesn't support it.

> How much of a pain would it be to make the legacy vs emulated vsyscall
> page a config option?

CONFIG_DONT_BREAK_MY_BINARIES? 

If anything runtime, but really for me it looks like the vsyscall
changes should be only in one of those limited compability paranoia 
patchkits.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/