Date: Sat, 12 Dec 2015 12:40:20 +0100 From: Heiko Carstens <heiko.carstens@...ibm.com> To: Kees Cook <keescook@...omium.org> Cc: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, Catalin Marinas <catalin.marinas@....com>, PaX Team <pageexec@...email.hu>, Michael Ellerman <mpe@...erman.id.au>, Ralf Baechle <ralf@...ux-mips.org> Subject: Re: Self Introduction On Thu, Dec 10, 2015 at 11:23:34AM -0800, Kees Cook wrote: > On Thu, Dec 10, 2015 at 11:07 AM, Daniel Micay <danielmicay@...il.com> wrote: > >> Yeah. PCID was Sandybridge and later? > > > > Yeah, that's right. And it defaults to the strong PCID implementation, > > but there's also a weaker but significantly faster PCID-based one. > > Is there anyone from Intel on the list? I would love to see UDEREF > ported to upstream on x86 (and the non PCID version too). No one has > stepped up to work on it yet. > > As for non-ARM and non-x86, IIRC s/390 has always had PAN, and I'd > love to update the matrix for powerpc and MIPS. > > http://kernsec.org/wiki/index.php/Exploit_Methods/Userspace_data_usage The statement for s390 is correct: we always had PAN in use. It's a hardware feature simply called "Address Spaces". The way we use it in Linux on s390 makes is impossible to access user space contents from kernel space without special instructions.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.