Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 9 Mar 2020 09:49:31 -0700
From: Guenter Roeck <>
To: Ard Biesheuvel <>
Cc:,,, Kees Cook <>,
	Emese Revfy <>, Arnd Bergmann <>,
	Laura Abbott <>,
Subject: Re: [PATCH v3] ARM: smp: add support for per-task stack canaries

On Thu, Dec 06, 2018 at 09:32:57AM +0100, Ard Biesheuvel wrote:
> On ARM, we currently only change the value of the stack canary when
> switching tasks if the kernel was built for UP. On SMP kernels, this
> is impossible since the stack canary value is obtained via a global
> symbol reference, which means
> a) all running tasks on all CPUs must use the same value
> b) we can only modify the value when no kernel stack frames are live
>    on any CPU, which is effectively never.
> So instead, use a GCC plugin to add a RTL pass that replaces each
> reference to the address of the __stack_chk_guard symbol with an
> expression that produces the address of the 'stack_canary' field
> that is added to struct thread_info. This way, each task will use
> its own randomized value.
> Cc: Russell King <>
> Cc: Kees Cook <>
> Cc: Emese Revfy <>
> Cc: Arnd Bergmann <>
> Cc: Laura Abbott <>
> Cc:
> Acked-by: Nicolas Pitre <>
> Signed-off-by: Ard Biesheuvel <>

Since this patch is in the tree, cc-option no longer works on
the arm architecture if CONFIG_STACKPROTECTOR_PER_TASK is enabled.

Any idea how to fix that ? 


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.