lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 2 Nov 2021 19:51:48 +0100
From:   Miguel Ojeda <>
To:     Nick Desaulniers <>
Cc:     Dan Li <>,
        Catalin Marinas <>,
        Will Deacon <>,
        Nathan Chancellor <>,
        Kees Cook <>,
        Thomas Gleixner <>,
        Andrew Morton <>,
        Peter Zijlstra <>,
        Sami Tolvanen <>,
        Masahiro Yamada <>,
        Mike Rapoport <>,
        Mark Rutland <>,,, Steven Rostedt <>,
        Viresh Kumar <>,,
        Colin King <>,
        Miguel Ojeda <>, Arnd Bergmann <>,
        Luc Van Oostenryck <>,
        Arvind Sankar <>,
        Marco Elver <>,
Subject: Re: [PATCH] [RFC/RFT] AARCH64: Add gcc Shadow Call Stack support

On Tue, Nov 2, 2021 at 7:42 PM Nick Desaulniers <> wrote:
> Do we want to move this to include/linux/compiler_attributes.h?
> Respecifying these repeatedly in each include/linux/compiler-*.h feels
> excessively redundant.

Note that they are spelled differently, which is one of the reasons to
keep them separate (and why I invoked my hopes of Clang and GCC

I typically mention that we could start breaking this "rule" and it
would be also reasonable; but on the other hand, having it this way
makes the distinction clear and also gives an incentive for compilers
to agree ;)

For reference, the file explains this on the top:

* Any other "attributes" (i.e. those that depend on a configuration option,
* on a compiler, on an architecture, on plugins, on other attributes...)
* should be defined elsewhere (e.g. compiler_types.h or compiler-*.h).
* The intention is to keep this file as simple as possible, as well as
* compiler- and version-agnostic (e.g. avoiding GCC_VERSION checks).


Powered by blists - more mailing lists