linux-kernel - Re: [PATCH 3/3] x86-64: Rework vsyscall emulation and add vsyscall= parameter

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: <4E42BDFF.5060507@zytor.com>
Date:	Wed, 10 Aug 2011 12:21:03 -0500
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Andy Lutomirski <luto@....edu>
CC:	x86@...nel.org, Andi Kleen <andi@...stfloor.org>,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	lueckintel@...oo.com, kimwooyoung@...il.com,
	Ingo Molnar <mingo@...e.hu>, Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH 3/3] x86-64: Rework vsyscall emulation and add vsyscall=
 parameter

On 08/10/2011 10:15 AM, Andy Lutomirski wrote:
> There are three choices:
> 
> vsyscall=native: Vsyscalls are native code that issues the
> corresponding syscalls.
> 
> vsyscall=emulate (default): Vsyscalls are emulated by instruction
> fault traps, tested in the bad_area path.  The actual contents of
> the vsyscall page is the same as the vsyscall=native case except
> that it's marked NX.  This way programs that make assumptions about
> what the code in the page does will not be confused when they read
> that code.
> 
> vsyscall=none: Trying to execute a vsyscall will segfault.
> 
> Signed-off-by: Andy Lutomirski <luto@....edu>

Hi Andy,

This patch doesn't apply.  What is your baseline for this patch?

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