Re: [PATCH] x86, vsyscall: add CONFIG to control default

2015-09-03 Thread Kees Cook
On Mon, Aug 31, 2015 at 2:23 PM, Andy Lutomirski wrote: > On Aug 31, 2015 1:13 PM, "Kees Cook" wrote: >> >> On Wed, Aug 12, 2015 at 7:23 PM, Josh Triplett wrote: >> > On Wed, Aug 12, 2015 at 05:55:19PM -0700, Kees Cook wrote: >> >> Most modern systems can run with vsyscall=none. In an effort to

Re: [PATCH] x86, vsyscall: add CONFIG to control default

2015-08-31 Thread Andy Lutomirski
On Aug 31, 2015 1:13 PM, "Kees Cook" wrote: > > On Wed, Aug 12, 2015 at 7:23 PM, Josh Triplett wrote: > > On Wed, Aug 12, 2015 at 05:55:19PM -0700, Kees Cook wrote: > >> Most modern systems can run with vsyscall=none. In an effort to provide > >> a way for build-time defaults to lack legacy setti

Re: [PATCH] x86, vsyscall: add CONFIG to control default

2015-08-31 Thread Kees Cook
On Wed, Aug 12, 2015 at 7:23 PM, Josh Triplett wrote: > On Wed, Aug 12, 2015 at 05:55:19PM -0700, Kees Cook wrote: >> 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 vs

Re: [PATCH] x86, vsyscall: add CONFIG to control default

2015-08-12 Thread Josh Triplett
On Wed, Aug 12, 2015 at 05:55:19PM -0700, Kees Cook wrote: > 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"

[PATCH] x86, vsyscall: add CONFIG to control default

2015-08-12 Thread Kees Cook
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 --- arch/x86/Kc