x86/entry/vsyscall: Add CONFIG to control default
authorKees Cook <keescook@chromium.org>
Thu, 13 Aug 2015 00:55:19 +0000 (17:55 -0700)
committerIngo Molnar <mingo@kernel.org>
Sun, 20 Sep 2015 08:31:06 +0000 (10:31 +0200)
commit3dc33bd30f3e1c1bcaaafa3482737694debf0f0b
treecd60ac8be186562ed7fd892ce2f1d016b8166702
parentc25be94f2870bf75552a41ad8b15f756e19ffb1d
x86/entry/vsyscall: Add CONFIG to control default

Most modern systems can run with vsyscall=none. In an effort to
provide a way for build-time defaults to lack legacy settings,
this adds a new CONFIG to select the type of vsyscall mapping to
use, similar to the existing "vsyscall" command line parameter.

Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Josh Triplett <josh@joshtriplett.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/20150813005519.GA11696@www.outflux.net
Signed-off-by: Ingo Molnar <mingo@kernel.org>
arch/x86/Kconfig
arch/x86/entry/vsyscall/vsyscall_64.c