Virtually mapped kernel stacks

Posted Jul 1, 2016 22:09 UTC (Fri) by corbet (editor, #1)
In reply to: Virtually mapped kernel stacks by nix
Parent article: Virtually mapped kernel stacks

The placement at the bottom was initially done so that it could be easily located just by aligning the stack pointer. It's not done that way anymore, so that doesn't matter much. Moving thread_info to the top would make it harder to overwrite, but doesn't solve the other problems that come with having it in that bit of memory. If you're going to change things, it seems better to just move it out entirely.