Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 23 Oct 2019 09:59:09 -0700
From: Sami Tolvanen <>
To: Mark Rutland <>, Masahiro Yamada <>
Cc: Will Deacon <>, Catalin Marinas <>, 
	Steven Rostedt <>, Ard Biesheuvel <>, 
	Dave Martin <>, Kees Cook <>, 
	Laura Abbott <>, Nick Desaulniers <>, 
	clang-built-linux <>, 
	Kernel Hardening <>, 
	linux-arm-kernel <>, LKML <>
Subject: Re: [PATCH 06/18] add support for Clang's Shadow Call Stack (SCS)

On Tue, Oct 22, 2019 at 9:28 AM Mark Rutland <> wrote:
> I think it would be preferable to follow the example of CC_FLAGS_FTRACE
> so that this can be filtered out, e.g.
> CFLAGS_SCS := -fsanitize=shadow-call-stack
> export CC_FLAGS_SCS
> endif
> ... with removal being:
> ... or:
> That way you only need to define the flags once, so the enable and
> disable falgs remain in sync by construction.

CFLAGS_REMOVE appears to be only implemented for objects, which means
there's no convenient way to filter out flags for everything in
arch/arm64/kvm/hyp, for example. I could add a CFLAGS_REMOVE
separately for each object file, or we could add something like
ccflags-remove-y to complement ccflags-y, which should be relatively
simple. Masahiro, do you have any suggestions?


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.