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
| ||
|
Date: Thu, 9 Nov 2017 11:04:02 -0800 From: Andy Lutomirski <luto@...nel.org> To: Dave Hansen <dave.hansen@...ux.intel.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>, moritz.lipp@...k.tugraz.at, Daniel Gruss <daniel.gruss@...k.tugraz.at>, michael.schwarz@...k.tugraz.at, richard.fellner@...dent.tugraz.at, Andrew Lutomirski <luto@...nel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Kees Cook <keescook@...gle.com>, Hugh Dickins <hughd@...gle.com>, X86 ML <x86@...nel.org> Subject: Re: [PATCH 24/30] x86, kaiser: disable native VSYSCALL On Wed, Nov 8, 2017 at 11:47 AM, Dave Hansen <dave.hansen@...ux.intel.com> wrote: > > From: Dave Hansen <dave.hansen@...ux.intel.com> > > The VSYSCALL page is mapped by kernel page tables at a kernel address. > It is troublesome to support with KAISER in place, so disable the > native case. > > Also add some help text about how KAISER might affect the emulation > case as well. Can you re-explain why this is helpful? Also, I'm about to send patches that may cause a rethinking of how KAISER handles the fixmap. --Andy > > Signed-off-by: Dave Hansen <dave.hansen@...ux.intel.com> > Cc: Moritz Lipp <moritz.lipp@...k.tugraz.at> > Cc: Daniel Gruss <daniel.gruss@...k.tugraz.at> > Cc: Michael Schwarz <michael.schwarz@...k.tugraz.at> > Cc: Richard Fellner <richard.fellner@...dent.tugraz.at> > Cc: Andy Lutomirski <luto@...nel.org> > Cc: Linus Torvalds <torvalds@...ux-foundation.org> > Cc: Kees Cook <keescook@...gle.com> > Cc: Hugh Dickins <hughd@...gle.com> > Cc: x86@...nel.org > > --- > > b/arch/x86/Kconfig | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff -puN arch/x86/Kconfig~kaiser-no-vsyscall arch/x86/Kconfig > --- a/arch/x86/Kconfig~kaiser-no-vsyscall 2017-11-08 10:45:39.157681370 -0800 > +++ b/arch/x86/Kconfig 2017-11-08 10:45:39.162681370 -0800 > @@ -2231,6 +2231,9 @@ choice > > config LEGACY_VSYSCALL_NATIVE > bool "Native" > + # The VSYSCALL page comes from the kernel page tables > + # and is not available when KAISER is enabled. > + depends on ! KAISER > help > Actual executable code is located in the fixed vsyscall > address mapping, implementing time() efficiently. Since > @@ -2248,6 +2251,11 @@ choice > exploits. This configuration is recommended when userspace > still uses the vsyscall area. > > + When KAISER is enabled, the vsyscall area will become > + unreadable. This emulation option still works, but KAISER > + will make it harder to do things like trace code using the > + emulation. > + > config LEGACY_VSYSCALL_NONE > bool "None" > help > _
Powered by blists - more mailing lists