+++ This bug was initially created as a clone of Bug #822300 +++ Description of problem: 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> Link: http://lkml.kernel.org/r/8449fb3abf89851fd6b2260972666a6f82542284.1312988155.git.luto@mit.edu Signed-off-by: H. Peter Anvin <hpa.com> Upstream commit: http://git.kernel.org/linus/3ae36655
git describe --contains 3ae36655 v3.1-rc2~16^2 We should tick with the default setting unless we notice -rt perf impacts in the future. Nothing to do here.