@@ -693,14 +693,18 @@ else
endif
endif
endif
+# If stack-protection was requested (and available, in the case of _AUTO),
+# then prepare the build for it being enabled.
ifdef stackp-name
- # If the stack protector has been selected, inform the rest of the build.
+ifneq ($(stackp-flag),)
+ # If the stack protector is active, enable code that depends on it.
KBUILD_CFLAGS += -DCONFIG_CC_STACKPROTECTOR
KBUILD_AFLAGS += -DCONFIG_CC_STACKPROTECTOR
# Find arch-specific stack protector compiler sanity-checking script.
stackp-path := $(srctree)/scripts/gcc-$(SRCARCH)_$(BITS)-has-stack-protector.sh
stackp-check := $(wildcard $(stackp-path))
endif
+endif
KBUILD_CFLAGS += $(stackp-flag)
ifeq ($(cc-name),clang)
There was a think-o in the logic for CONFIG_CC_STACKPROTECTOR_AUTO, which would leave CONFIG_CC_STACKPROTECTOR defined when a compiler didn't support stack-protector. This usually won't cause a problem with a build, but it's not correct, and shouldn't happen. Reported-by: Mark Rutland <mark.rutland@arm.com> Cc: Masahiro Yamada <yamada.masahiro@socionext.com> Cc: linux-kbuild@vger.kernel.org Signed-off-by: Kees Cook <keescook@chromium.org> --- Andrew, if possible, can you squash this as a fix for the mmots patch "makefile-introduce-config_cc_stackprotector_auto.patch"? If not, that's fine. --- Makefile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)