]> git.baikalelectronics.ru Git - kernel.git/commit
hardening: Avoid harmless Clang option under CONFIG_INIT_STACK_ALL_ZERO
authorKees Cook <keescook@chromium.org>
Tue, 14 Sep 2021 19:49:03 +0000 (12:49 -0700)
committerKees Cook <keescook@chromium.org>
Sat, 25 Sep 2021 15:22:59 +0000 (08:22 -0700)
commit4184c70d46c79a587164121d098777e48f03192c
tree3743423cb2beaf8ff6638895827ffadd913723a8
parent77c55e5e0599360cc5f212ae9b228ab6c429f652
hardening: Avoid harmless Clang option under CONFIG_INIT_STACK_ALL_ZERO

Currently under Clang, CC_HAS_AUTO_VAR_INIT_ZERO requires an extra
-enable flag compared to CC_HAS_AUTO_VAR_INIT_PATTERN. GCC 12[1] will
not, and will happily ignore the Clang-specific flag. However, its
presence on the command-line is both cumbersome and confusing. Due to
GCC's tolerant behavior, though, we can continue to use a single Kconfig
cc-option test for the feature on both compilers, but then drop the
Clang-specific option in the Makefile.

In other words, this patch does not change anything other than making the
compiler command line shorter once GCC supports -ftrivial-auto-var-init=zero.

[1] https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=a25e0b5e6ac8a77a71c229e0a7b744603365b0e9

Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: llvm@lists.linux.dev
Fixes: 303bacfb8b2f ("hardening: Clarify Kconfig text for auto-var-init")
Suggested-by: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/lkml/20210914102837.6172-1-will@kernel.org/
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Acked-by: Will Deacon <will@kernel.org>
Signed-off-by: Kees Cook <keescook@chromium.org>
Makefile
security/Kconfig.hardening