From: Greg Kroah-Hartman Date: Thu, 11 Aug 2022 11:55:46 +0000 (+0200) Subject: 4.19-stable patches X-Git-Tag: v5.15.61~245 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6e2b26d9d221230327aeb9cc3de8d4855dd8c8fa;p=thirdparty%2Fkernel%2Fstable-queue.git 4.19-stable patches added patches: makefile-link-with-z-noexecstack-no-warn-rwx-segments.patch --- diff --git a/queue-4.19/makefile-link-with-z-noexecstack-no-warn-rwx-segments.patch b/queue-4.19/makefile-link-with-z-noexecstack-no-warn-rwx-segments.patch new file mode 100644 index 00000000000..7f893762687 --- /dev/null +++ b/queue-4.19/makefile-link-with-z-noexecstack-no-warn-rwx-segments.patch @@ -0,0 +1,59 @@ +From 0d362be5b14200b77ecc2127936a5ff82fbffe41 Mon Sep 17 00:00:00 2001 +From: Nick Desaulniers +Date: Wed, 10 Aug 2022 15:24:40 -0700 +Subject: Makefile: link with -z noexecstack --no-warn-rwx-segments + +From: Nick Desaulniers + +commit 0d362be5b14200b77ecc2127936a5ff82fbffe41 upstream. + +Users of GNU ld (BFD) from binutils 2.39+ will observe multiple +instances of a new warning when linking kernels in the form: + + ld: warning: vmlinux: missing .note.GNU-stack section implies executable stack + ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker + ld: warning: vmlinux has a LOAD segment with RWX permissions + +Generally, we would like to avoid the stack being executable. Because +there could be a need for the stack to be executable, assembler sources +have to opt-in to this security feature via explicit creation of the +.note.GNU-stack feature (which compilers create by default) or command +line flag --noexecstack. Or we can simply tell the linker the +production of such sections is irrelevant and to link the stack as +--noexecstack. + +LLVM's LLD linker defaults to -z noexecstack, so this flag isn't +strictly necessary when linking with LLD, only BFD, but it doesn't hurt +to be explicit here for all linkers IMO. --no-warn-rwx-segments is +currently BFD specific and only available in the current latest release, +so it's wrapped in an ld-option check. + +While the kernel makes extensive usage of ELF sections, it doesn't use +permissions from ELF segments. + +Link: https://lore.kernel.org/linux-block/3af4127a-f453-4cf7-f133-a181cce06f73@kernel.dk/ +Link: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=ba951afb99912da01a6e8434126b8fac7aa75107 +Link: https://github.com/llvm/llvm-project/issues/57009 +Reported-and-tested-by: Jens Axboe +Suggested-by: Fangrui Song +Signed-off-by: Nick Desaulniers +Signed-off-by: Linus Torvalds +Signed-off-by: Greg Kroah-Hartman +--- + Makefile | 5 +++++ + 1 file changed, 5 insertions(+) + +--- a/Makefile ++++ b/Makefile +@@ -876,6 +876,11 @@ LDFLAGS_BUILD_ID := $(call ld-option, -- + KBUILD_LDFLAGS_MODULE += $(LDFLAGS_BUILD_ID) + LDFLAGS_vmlinux += $(LDFLAGS_BUILD_ID) + ++KBUILD_LDFLAGS += -z noexecstack ++ifeq ($(CONFIG_LD_IS_BFD),y) ++KBUILD_LDFLAGS += $(call ld-option,--no-warn-rwx-segments) ++endif ++ + ifeq ($(CONFIG_STRIP_ASM_SYMS),y) + LDFLAGS_vmlinux += $(call ld-option, -X,) + endif