From: Will Deacon <will@kernel.org>
To: Sami Tolvanen <samitolvanen@google.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Kees Cook <keescook@chromium.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org, James Morse <james.morse@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] scs: switch to vmapped shadow stacks
Date: Mon, 30 Nov 2020 11:44:17 +0000 [thread overview]
Message-ID: <20201130114417.GA24563@willie-the-truck> (raw)
In-Reply-To: <20201124195940.27061-2-samitolvanen@google.com>
On Tue, Nov 24, 2020 at 11:59:39AM -0800, Sami Tolvanen wrote:
> The kernel currently uses kmem_cache to allocate shadow call stacks,
> which means an overflows 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 for
> tasks, which increases shadow stack size to a full page and provides
> more robust overflow detection, similarly to VMAP_STACK.
>
> Signed-off-by: Sami Tolvanen <samitolvanen@google.com>
> ---
> include/linux/scs.h | 12 ++++-----
> kernel/scs.c | 66 +++++++++++++++++++++++++++++++++++++--------
> 2 files changed, 61 insertions(+), 17 deletions(-)
>
> diff --git a/include/linux/scs.h b/include/linux/scs.h
> index 6dec390cf154..2a506c2a16f4 100644
> --- a/include/linux/scs.h
> +++ b/include/linux/scs.h
> @@ -15,12 +15,8 @@
>
> #ifdef CONFIG_SHADOW_CALL_STACK
>
> -/*
> - * In testing, 1 KiB shadow stack size (i.e. 128 stack frames on a 64-bit
> - * architecture) provided ~40% safety margin on stack usage while keeping
> - * memory allocation overhead reasonable.
> - */
> -#define SCS_SIZE SZ_1K
> +#define SCS_ORDER 0
> +#define SCS_SIZE (PAGE_SIZE << SCS_ORDER)
> #define GFP_SCS (GFP_KERNEL | __GFP_ZERO)
>
> /* An illegal pointer value to mark the end of the shadow stack. */
> @@ -33,6 +29,8 @@
> #define task_scs(tsk) (task_thread_info(tsk)->scs_base)
> #define task_scs_sp(tsk) (task_thread_info(tsk)->scs_sp)
>
> +void *scs_alloc(int node);
> +void scs_free(void *s);
> void scs_init(void);
> int scs_prepare(struct task_struct *tsk, int node);
> void scs_release(struct task_struct *tsk);
> @@ -61,6 +59,8 @@ static inline bool task_scs_end_corrupted(struct task_struct *tsk)
>
> #else /* CONFIG_SHADOW_CALL_STACK */
>
> +static inline void *scs_alloc(int node) { return NULL; }
> +static inline void scs_free(void *s) {}
> static inline void scs_init(void) {}
> static inline void scs_task_reset(struct task_struct *tsk) {}
> static inline int scs_prepare(struct task_struct *tsk, int node) { return 0; }
> diff --git a/kernel/scs.c b/kernel/scs.c
> index 4ff4a7ba0094..25b0dd5aa0e2 100644
> --- a/kernel/scs.c
> +++ b/kernel/scs.c
> @@ -5,50 +5,94 @@
> * Copyright (C) 2019 Google LLC
> */
>
> +#include <linux/cpuhotplug.h>
> #include <linux/kasan.h>
> #include <linux/mm.h>
> #include <linux/scs.h>
> -#include <linux/slab.h>
> +#include <linux/vmalloc.h>
> #include <linux/vmstat.h>
>
> -static struct kmem_cache *scs_cache;
> -
> static void __scs_account(void *s, int account)
> {
> - struct page *scs_page = virt_to_page(s);
> + struct page *scs_page = vmalloc_to_page(s);
>
> mod_node_page_state(page_pgdat(scs_page), NR_KERNEL_SCS_KB,
> account * (SCS_SIZE / SZ_1K));
> }
>
> -static void *scs_alloc(int node)
> +/* Matches NR_CACHED_STACKS for VMAP_STACK */
> +#define NR_CACHED_SCS 2
> +static DEFINE_PER_CPU(void *, scs_cache[NR_CACHED_SCS]);
> +
> +void *scs_alloc(int node)
> {
> - void *s = kmem_cache_alloc_node(scs_cache, GFP_SCS, node);
> + int i;
> + void *s;
> +
> + for (i = 0; i < NR_CACHED_SCS; i++) {
> + s = this_cpu_xchg(scs_cache[i], NULL);
> + if (s) {
> + kasan_unpoison_vmalloc(s, SCS_SIZE);
> + memset(s, 0, SCS_SIZE);
> + goto out;
> + }
> + }
> +
> + s = __vmalloc_node_range(SCS_SIZE, 1, VMALLOC_START, VMALLOC_END,
> + GFP_SCS, PAGE_KERNEL, 0, node,
> + __builtin_return_address(0));
>
> if (!s)
> return NULL;
Sorry I didn't spot this before, but if you put the xchg/vmalloc code
into a new __scs_alloc() function then you can drop the label and this
becomes:
s = __scs_alloc(...);
if (!s)
return NULL;
*__scs_maghic(s) = SCS_ENG_MAGIC;
...
With that:
Acked-by: Will Deacon <will@kernel.org>
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-30 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 19:59 [PATCH v2 0/2] scs: switch to vmapped shadow stacks Sami Tolvanen
2020-11-24 19:59 ` [PATCH v2 1/2] " Sami Tolvanen
2020-11-24 22:04 ` Kees Cook
2020-11-30 11:44 ` Will Deacon [this message]
2020-11-30 20:03 ` Sami Tolvanen
2020-11-24 19:59 ` [PATCH v2 2/2] arm64: scs: use vmapped IRQ and SDEI " Sami Tolvanen
2020-11-30 11:49 ` Will Deacon
2020-11-30 21:13 ` Sami Tolvanen
2020-12-01 10:18 ` Will Deacon
2020-12-01 10:26 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201130114417.GA24563@willie-the-truck \
--to=will@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=samitolvanen@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox