]> git.ipfire.org Git - thirdparty/linux.git/commit - Makefile
security: Implement Clang's stack initialization
authorKees Cook <keescook@chromium.org>
Wed, 10 Apr 2019 15:48:31 +0000 (08:48 -0700)
committerKees Cook <keescook@chromium.org>
Wed, 24 Apr 2019 21:00:56 +0000 (14:00 -0700)
commit709a972efb01efaeb97cad1adc87fe400119c8ab
tree395292ab51f012c21b436c404811e810bc863b4d
parentb6a6a3772d20b8552e703bb2a651760a22167cf6
security: Implement Clang's stack initialization

CONFIG_INIT_STACK_ALL turns on stack initialization based on
-ftrivial-auto-var-init in Clang builds, which has greater coverage
than CONFIG_GCC_PLUGINS_STRUCTLEAK_BYREF_ALL.

-ftrivial-auto-var-init Clang option provides trivial initializers for
uninitialized local variables, variable fields and padding.

It has three possible values:
  pattern - uninitialized locals are filled with a fixed pattern
    (mostly 0xAA on 64-bit platforms, see https://reviews.llvm.org/D54604
    for more details, but 0x000000AA for 32-bit pointers) likely to cause
    crashes when uninitialized value is used;
  zero (it's still debated whether this flag makes it to the official
    Clang release) - uninitialized locals are filled with zeroes;
  uninitialized (default) - uninitialized locals are left intact.

This patch uses only the "pattern" mode when CONFIG_INIT_STACK_ALL is
enabled.

Developers have the possibility to opt-out of this feature on a
per-variable basis by using __attribute__((uninitialized)), but such
use should be well justified in comments.

Co-developed-by: Alexander Potapenko <glider@google.com>
Signed-off-by: Alexander Potapenko <glider@google.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Alexander Potapenko <glider@google.com>
Acked-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Makefile
security/Kconfig.hardening