[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrWMh0+_RKV1OwwqE6s8P=fLFUYcAxvSNwDK_qB6BOBs9w@mail.gmail.com>
Date: Tue, 14 Jun 2016 23:01:19 -0700
From: Andy Lutomirski <luto@...capital.net>
To: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, Kees Cook <keescook@...omium.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org>,
Borislav Petkov <bp@...en8.de>, "linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Playing with virtually mapped stacks (with guard pages!)
Hi all-
If you want to play with virtually mapped stacks, I have it more or
less working on x86 in a branch here:
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=x86/vmap_stack
The core bit (virtually map the stack and fix the accounting) is just
a config option, but it needs the arch to opt-in. I suspect that
every arch will have its own set of silly issues to address to make it
work well. For x86, the silly issues are getting the OOPS to work
right and handling some vmalloc_fault oddities to avoid panicing at
random.
--Andy
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.
