Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1422619
| From | Andy Lutomirski <luto@amacapital.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Playing with virtually mapped stacks (with guard pages!) |
| Date | 2016-06-15 08:10 +0200 |
| Message-ID | <rKcbw-7f2-11@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Playing with virtually mapped stacks (with guard pages!) Andy Lutomirski <luto@amacapital.net> - 2016-06-15 08:10 +0200
Re: Playing with virtually mapped stacks (with guard pages!) Kees Cook <keescook@chromium.org> - 2016-06-15 19:10 +0200
Re: Playing with virtually mapped stacks (with guard pages!) Andy Lutomirski <luto@amacapital.net> - 2016-06-15 19:30 +0200
Re: Playing with virtually mapped stacks (with guard pages!) Kees Cook <keescook@chromium.org> - 2016-06-15 19:50 +0200
csiph-web