Re: [PATCH 1/2] scs: switch to vmapped shadow stacks

2020-11-23 Thread Will Deacon
Hi Sami, On Fri, Nov 20, 2020 at 09:00:17AM -0800, Sami Tolvanen wrote: > On Thu, Nov 19, 2020 at 5:00 AM Will Deacon wrote: > > On Thu, Oct 22, 2020 at 01:23:54PM -0700, Sami Tolvanen wrote: > > > The kernel currently uses kmem_cache to allocate shadow call stacks, > > > which means an overflow

Re: [PATCH 1/2] scs: switch to vmapped shadow stacks

2020-11-20 Thread Sami Tolvanen
On Thu, Nov 19, 2020 at 5:00 AM Will Deacon wrote: > > Hi Sami, > > On Thu, Oct 22, 2020 at 01:23:54PM -0700, Sami Tolvanen wrote: > > The kernel currently uses kmem_cache to allocate shadow call stacks, > > which means an overflow may not be immediately detected and can > > potentially result in

Re: [PATCH 1/2] scs: switch to vmapped shadow stacks

2020-11-19 Thread Will Deacon
Hi Sami, On Thu, Oct 22, 2020 at 01:23:54PM -0700, Sami Tolvanen wrote: > The kernel currently uses kmem_cache to allocate shadow call stacks, > which means an overflow may not be immediately detected and can > potentially result in another task's shadow stack to be overwritten. > > This change

Re: [PATCH 1/2] scs: switch to vmapped shadow stacks

2020-10-22 Thread Kees Cook
On Thu, Oct 22, 2020 at 01:23:54PM -0700, Sami Tolvanen wrote: > The kernel currently uses kmem_cache to allocate shadow call stacks, > which means an overflow may not be immediately detected and can > potentially result in another task's shadow stack to be overwritten. > > This change switches

[PATCH 1/2] scs: switch to vmapped shadow stacks

2020-10-22 Thread Sami Tolvanen
The kernel currently uses kmem_cache to allocate shadow call stacks, which means an overflow may not be immediately detected and can potentially result in another task's shadow stack to be overwritten. This change switches SCS to use virtually mapped shadow stacks, which increases shadow stack