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: <4E3C5460.90505@zytor.com>
Date:	Fri, 05 Aug 2011 13:36:48 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	luto@....edu, 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 08/05/2011 01:26 PM, Andi Kleen wrote:
>> I have to say I believe that trying to JIT the vdso or vsyscall pages is
>> extremely dubious at best.  They are fundamentally different from normal
>> user space in that the kernel can muck with them any time, without
>> notifying userspace about it.  The other aspect of this is that this is
>> about the legacy vsyscall page, which we're trying to get rid of, partly
>> because of security problems.
> 
> There's clear evidence now you can't: it's used even by new binaries.

time() is not supported by vdso; this is a problem.  Getting rid of it
is a long-term thing.

	-hpa

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