diff options
author | 2025-02-16 01:15:52 +0900 | |
---|---|---|
committer | 2025-03-15 21:19:44 +0900 | |
commit | c15253494fd98cd76250c9faaebbc8b45f7d0072 (patch) | |
tree | 4f940fdfa9e798035632fc0ce37393b03c9f2732 /Makefile | |
parent | scripts: make python shebangs specific about desired version (diff) | |
download | wireguard-linux-c15253494fd98cd76250c9faaebbc8b45f7d0072.tar.xz wireguard-linux-c15253494fd98cd76250c9faaebbc8b45f7d0072.zip |
kbuild: move -fzero-init-padding-bits=all to the top-level Makefile
The -fzero-init-padding-bits=all option is not a warning flag, so
defining it in scripts/Makefile.extrawarn is inconsistent.
Move it to the top-level Makefile for consistency.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Reviewed-by: Kees Cook <kees@kernel.org>
Diffstat (limited to 'Makefile')
-rw-r--r-- | Makefile | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -928,6 +928,9 @@ KBUILD_CFLAGS += $(CC_AUTO_VAR_INIT_ZERO_ENABLER) endif endif +# Explicitly clear padding bits during variable initialization +KBUILD_CFLAGS += $(call cc-option,-fzero-init-padding-bits=all) + # While VLAs have been removed, GCC produces unreachable stack probes # for the randomize_kstack_offset feature. Disable it for all compilers. KBUILD_CFLAGS += $(call cc-option, -fno-stack-clash-protection) |