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  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]
Date:   Thu, 2 Nov 2017 19:40:27 +0100 (CET)
From:   Thomas Gleixner <>
To:     Linus Torvalds <>
cc:     Andy Lutomirski <>,
        Dave Hansen <>,
        Andy Lutomirski <>,
        "" <>,
        "" <>,,
        Daniel Gruss <>,, Kees Cook <>,
        Hugh Dickins <>, X86 ML <>
Subject: Re: [PATCH 02/23] x86, kaiser: do not set _PAGE_USER for init_mm
 page tables

On Thu, 2 Nov 2017, Linus Torvalds wrote:

> On Thu, Nov 2, 2017 at 11:19 AM, Andy Lutomirski <> wrote:
> >
> > We'd have to force NONE, and Linus won't like it.
> Oh, I think it's fine for the kaiser case.
> I am not convinced anybody will actually use it, but if you do use it,
> I suspect "the legacy vsyscall page no longer works" is the least of
> your worries.
> That said, I think you can keep emulation, and just make it
> unreadable. That will keep legacy binaries still working, and will
> break a much smaller subset. So we have four cases:
>  - native
>  - read-only emulation
>  - unreadable emulation
>  - none
> and kaiser triggering that unreadable case sounds like the option
> least likely to cause trouble. vsyscalls still work, anybody who tries
> to trace them and look at the code will not.

Hmm. Not sure. IIRC you need to be able to read it to figure out where the
entry points are. They are at fixed offsets, but there is some voodoo out
there which reads the 'elf' to get to them.



Powered by blists - more mailing lists