Buildresult: linus-rand/arm64-randconfig/arm64-gcc5 built on Nov 4 2021, 08:54

kisskb

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

Status:	OK
Date/Time:	Nov 4 2021, 08:54
Duration:	0:05:42.851977
Builder:	blade46
Revision:	Merge branch 'per_signal_struct_coredumps-for-v5.16' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace (`a602285ac11b019e9ce7c3907328e9f95f4967f0)`
Target:	linus-rand/arm64-randconfig/arm64-gcc5
Branch:	linus-rand
Compiler:	arm64-gcc5 (aarch64-linux-gcc.br_real (Buildroot 2016.11-git-00613-ge98b4dd) 5.4.0 / GNU ld (GNU Binutils) 2.25.1)
Config:	randconfig (download)
Log:	Download original Possible warnings (6) .config:5972:warning: override: reassigning to symbol PREVENT_FIRMWARE_BUILD warning: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum warning: LSE atomics not supported by binutils arch/arm64/boot/dts/qcom/sm6125.dtsi:497.19-503.6: Warning (unit_address_format): /soc/timer@f120000/frame@0f121000: unit name should not have leading 0s arch/arm64/boot/dts/qcom/sm6125.dtsi:505.19-510.6: Warning (unit_address_format): /soc/timer@f120000/frame@0f123000: unit name should not have leading 0s arch/arm64/boot/dts/qcom/sm6125.dtsi:512.19-517.6: Warning (unit_address_format): /soc/timer@f120000/frame@0f124000: unit name should not have leading 0s Full Log # git rev-parse -q --verify a602285ac11b019e9ce7c3907328e9f95f4967f0^{commit} a602285ac11b019e9ce7c3907328e9f95f4967f0 already have revision, skipping fetch # git checkout -q -f -B kisskb a602285ac11b019e9ce7c3907328e9f95f4967f0 # git clean -qxdf # < git log -1 # commit a602285ac11b019e9ce7c3907328e9f95f4967f0 # Merge: 5c4e0a21fae8 3f66f86bfed3 # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Wed Nov 3 12:15:29 2021 -0700 # # Merge branch 'per_signal_struct_coredumps-for-v5.16' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace # # Pull per signal_struct coredumps from Eric Biederman: # "Current coredumps are mixed up with the exit code, the signal handling # code, and the ptrace code making coredumps much more complicated than # necessary and difficult to follow. # # This series of changes starts with ptrace_stop and cleans it up, # making it easier to follow what is happening in ptrace_stop. Then # cleans up the exec interactions with coredumps. Then cleans up the # coredump interactions with exit. Finally the coredump interactions # with the signal handling code is cleaned up. # # The first and last changes are bug fixes for minor bugs. # # I believe the fact that vfork followed by execve can kill the process # the called vfork if exec fails is sufficient justification to change # the userspace visible behavior. # # In previous discussions some of these changes were organized # differently and individually appeared to make the code base worse. As # currently written I believe they all stand on their own as cleanups # and bug fixes. # # Which means that even if the worst should happen and the last change # needs to be reverted for some unimaginable reason, the code base will # still be improved. # # If the worst does not happen there are a more cleanups that can be # made. Signals that generate coredumps can easily become eligible for # short circuit delivery in complete_signal. The entire rendezvous for # generating a coredump can move into get_signal. The function # force_sig_info_to_task be written in a way that does not modify the # signal handling state of the target task (because coredumps are # eligible for short circuit delivery). Many of these future cleanups # can be done another way but nothing so cleanly as if coredumps become # per signal_struct" # # * 'per_signal_struct_coredumps-for-v5.16' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace: # coredump: Limit coredumps to a single thread group # coredump: Don't perform any cleanups before dumping core # exit: Factor coredump_exit_mm out of exit_mm # exec: Check for a pending fatal signal instead of core_state # ptrace: Remove the unnecessary arguments from arch_ptrace_stop # signal: Remove the bogus sigkill_pending in ptrace_stop # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-gcc --version # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-ld --version # < git log --format=%s --max-count=1 a602285ac11b019e9ce7c3907328e9f95f4967f0 # < make -s -j 32 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- randconfig # Added to kconfig CONFIG_PREVENT_FIRMWARE_BUILD=y # < make -s -j 32 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- help # make -s -j 32 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- olddefconfig .config:5972:warning: override: reassigning to symbol PREVENT_FIRMWARE_BUILD # make -s -j 32 ARCH=arm64 O=/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- warning: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum warning: LSE atomics not supported by binutils /kisskb/src/arch/arm64/boot/dts/qcom/sm6125.dtsi:497.19-503.6: Warning (unit_address_format): /soc/timer@f120000/frame@0f121000: unit name should not have leading 0s /kisskb/src/arch/arm64/boot/dts/qcom/sm6125.dtsi:505.19-510.6: Warning (unit_address_format): /soc/timer@f120000/frame@0f123000: unit name should not have leading 0s /kisskb/src/arch/arm64/boot/dts/qcom/sm6125.dtsi:512.19-517.6: Warning (unit_address_format): /soc/timer@f120000/frame@0f124000: unit name should not have leading 0s Completed OK # rm -rf /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 # Build took: 0:05:42.851977

© Michael Ellerman 2006-2018.