Buildresult: linus-rand/arm64-randconfig/arm64-gcc5 built on Oct 15 2020, 10:29

kisskb

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

Status:	Failed
Date/Time:	Oct 15 2020, 10:29
Duration:	0:00:12.021196
Builder:	ka4
Revision:	Merge tag 'threads-v5.10' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux (`4da9af0014b51c8b015ed8c622440ef28912efe6)`
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 errors /usr/bin/env: 'python3': No such file or directory make[4]: * [Makefile:187: /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4/tools/bpf/resolve_btfids/bpf_helper_defs.h] Error 127 make[3]: * [Makefile:54: /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4/tools/bpf/resolve_btfids//libbpf.a] Error 2 make[2]: * [Makefile:71: bpf/resolve_btfids] Error 2 make[1]: * [Makefile:1877: tools/bpf/resolve_btfids] Error 2 make: *** [Makefile:185: __sub-make] Error 2 Possible warnings (6) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) Full Log # git rev-parse -q --verify 4da9af0014b51c8b015ed8c622440ef28912efe6^{commit} # git fetch -q -n -f git://fs.ozlabs.ibm.com/kernel/linus master # git rev-parse -q --verify 4da9af0014b51c8b015ed8c622440ef28912efe6^{commit} 4da9af0014b51c8b015ed8c622440ef28912efe6 # git checkout -q -f -B kisskb 4da9af0014b51c8b015ed8c622440ef28912efe6 # git clean -qxdf # < git log -1 # commit 4da9af0014b51c8b015ed8c622440ef28912efe6 # Merge: 612e7a4c1645 01361b665a26 # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Wed Oct 14 14:39:20 2020 -0700 # # Merge tag 'threads-v5.10' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux # # Pull pidfd updates from Christian Brauner: # "This introduces a new extension to the pidfd_open() syscall. Users can # now raise the new PIDFD_NONBLOCK flag to support non-blocking pidfd # file descriptors. This has been requested for uses in async process # management libraries such as async-pidfd in Rust. # # Ever since the introduction of pidfds and more advanced async io # various programming languages such as Rust have grown support for # async event libraries. These libraries are created to help build # epoll-based event loops around file descriptors. A common pattern is # to automatically make all file descriptors they manage to O_NONBLOCK. # # For such libraries the EAGAIN error code is treated specially. When a # function is called that returns EAGAIN the function isn't called again # until the event loop indicates the the file descriptor is ready. # Supporting EAGAIN when waiting on pidfds makes such libraries just # work with little effort. # # This introduces a new flag PIDFD_NONBLOCK that is equivalent to # O_NONBLOCK. This follows the same patterns we have for other (anon # inode) file descriptors such as EFD_NONBLOCK, IN_NONBLOCK, # SFD_NONBLOCK, TFD_NONBLOCK and the same for close-on-exec flags. # # Passing a non-blocking pidfd to waitid() currently has no effect, i.e. # is not supported. There are users which would like to use waitid() on # pidfds that are O_NONBLOCK and mix it with pidfds that are blocking # and both pass them to waitid(). # # The expected behavior is to have waitid() return -EAGAIN for # non-blocking pidfds and to block for blocking pidfds without needing # to perform any additional checks for flags set on the pidfd before # passing it to waitid(). Non-blocking pidfds will return EAGAIN from # waitid() when no child process is ready yet. Returning -EAGAIN for # non-blocking pidfds makes it easier for event loops that handle EAGAIN # specially. # # It also makes the API more consistent and uniform. In essence, # waitid() is treated like a read on a non-blocking pidfd or a recvmsg() # on a non-blocking socket. # # With the addition of support for non-blocking pidfds we support the # same functionality that sockets do. For sockets() recvmsg() supports # MSG_DONTWAIT for pidfds waitid() supports WNOHANG. Both flags are # per-call options. In contrast non-blocking pidfds and non-blocking # sockets are a setting on an open file description affecting all # threads in the calling process as well as other processes that hold # file descriptors referring to the same open file description. Both # behaviors, per call and per open file description, have genuine # use-cases. # # The interaction with the WNOHANG flag is documented as follows: # # - If a non-blocking pidfd is passed and WNOHANG is not raised we # simply raise the WNOHANG flag internally. When do_wait() returns # indicating that there are eligible child processes but none have # exited yet we set EAGAIN. If no child process exists we continue # returning ECHILD. # # - If a non-blocking pidfd is passed and WNOHANG is raised waitid() # will continue returning 0, i.e. it will not set EAGAIN. This ensure # backwards compatibility with applications passing WNOHANG # explicitly with pidfds" # # * tag 'threads-v5.10' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux: # tests: remove O_NONBLOCK before waiting for WSTOPPED # tests: add waitid() tests for non-blocking pidfds # tests: port pidfd_wait to kselftest harness # pidfd: support PIDFD_NONBLOCK in pidfd_open() # exit: support non-blocking pidfds # < /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 4da9af0014b51c8b015ed8c622440ef28912efe6 # < make -s -j 10 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 KCONFIG_SEED=0x397B2216 # Added to kconfig CONFIG_PREVENT_FIRMWARE_BUILD=y # yes \n \| make -s -j 10 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- oldconfig yes: standard output: Broken pipe # make -s -j 10 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- arch/arm64/Makefile:25: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:25: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum Auto-detecting system features: ... libelf: [ [32mon[m ] ... zlib: [ [32mon[m ] ... bpf: [ [32mon[m ] /usr/bin/env: 'python3': No such file or directory make[4]: * [Makefile:187: /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4/tools/bpf/resolve_btfids/bpf_helper_defs.h] Error 127 make[4]: * Deleting file '/kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4/tools/bpf/resolve_btfids/bpf_helper_defs.h' make[3]: * [Makefile:54: /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4/tools/bpf/resolve_btfids//libbpf.a] Error 2 make[3]: * Waiting for unfinished jobs.... make[2]: * [Makefile:71: bpf/resolve_btfids] Error 2 make[1]: * [/kisskb/src/Makefile:1877: tools/bpf/resolve_btfids] Error 2 make[1]: * Waiting for unfinished jobs.... /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) make: * [Makefile:185: __sub-make] Error 2 Command 'make -s -j 10 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- ' returned non-zero exit status 2 # rm -rf /kisskb/build/linus-rand_arm64-randconfig_arm64-gcc5.4 # Build took: 0:00:12.021196

© Michael Ellerman 2006-2018.