Buildresult: linus/riscv-defconfig/riscv-gcc11 built on Aug 11 2022, 13:24

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Aug 11 2022, 13:24
Duration:	0:05:21.595534
Builder:	ka2
Revision:	x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments (`ffcf9c5700e49c0aee42dcba9a12ba21338e8136)`
Target:	linus/riscv-defconfig/riscv-gcc11
Branch:	linus
Compiler:	riscv-gcc11 (riscv64-linux-gcc (GCC) 11.1.0 / GNU ld (GNU Binutils) 2.36.1)
Config:	defconfig (download)
Log:	Download original No warnings found in log. Full Log # git rev-parse -q --verify ffcf9c5700e49c0aee42dcba9a12ba21338e8136^{commit} ffcf9c5700e49c0aee42dcba9a12ba21338e8136 already have revision, skipping fetch # git checkout -q -f -B kisskb ffcf9c5700e49c0aee42dcba9a12ba21338e8136 # git clean -qxdf # < git log -1 # commit ffcf9c5700e49c0aee42dcba9a12ba21338e8136 # Author: Nick Desaulniers <ndesaulniers@google.com> # Date: Wed Aug 10 15:24:41 2022 -0700 # # x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments # # 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: arch/x86/boot/pmjump.o: 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: arch/x86/boot/compressed/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 <axboe@kernel.dk> # Suggested-by: Fangrui Song <maskray@google.com> # Signed-off-by: Nick Desaulniers <ndesaulniers@google.com> # Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/korg/gcc-11.1.0-nolibc/riscv64-linux/bin/riscv64-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-11.1.0-nolibc/riscv64-linux/bin/riscv64-linux-ld --version # < git log --format=%s --max-count=1 ffcf9c5700e49c0aee42dcba9a12ba21338e8136 # < make -s -j 8 ARCH=riscv O=/kisskb/build/linus_riscv-defconfig_riscv-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.1.0-nolibc/riscv64-linux/bin/riscv64-linux- defconfig # < make -s -j 8 ARCH=riscv O=/kisskb/build/linus_riscv-defconfig_riscv-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.1.0-nolibc/riscv64-linux/bin/riscv64-linux- help # make -s -j 8 ARCH=riscv O=/kisskb/build/linus_riscv-defconfig_riscv-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.1.0-nolibc/riscv64-linux/bin/riscv64-linux- olddefconfig # make -s -j 8 ARCH=riscv O=/kisskb/build/linus_riscv-defconfig_riscv-gcc11 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-11.1.0-nolibc/riscv64-linux/bin/riscv64-linux- Completed OK # rm -rf /kisskb/build/linus_riscv-defconfig_riscv-gcc11 # Build took: 0:05:21.595534

© Michael Ellerman 2006-2018.