Buildresult: powerpc-fixes/arm64-defconfig/arm64-gcc5 built on Nov 2 2020, 23:06

kisskb

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

Status:	OK
Date/Time:	Nov 2 2020, 23:06
Duration:	0:06:11.484420
Builder:	ka3
Revision:	powerpc/smp: Call rcu_cpu_starting() earlier (`99f070b62322a4b8c1252952735806d09eb44b68)`
Target:	powerpc-fixes/arm64-defconfig/arm64-gcc5
Branch:	powerpc-fixes
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:	defconfig (download)
Log:	Download original Possible warnings (8) 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) arch/arm64/boot/dts/qcom/ipq6018.dtsi:185.3-14: Warning (dma_ranges_format): /soc:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) arch/arm64/boot/dts/qcom/ipq6018.dtsi:185.3-14: Warning (dma_ranges_format): /soc:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) Full Log # git rev-parse -q --verify 99f070b62322a4b8c1252952735806d09eb44b68^{commit} # git fetch -q -n -f git://gitlab.ozlabs.ibm.com/linuxppc/linux.git fixes-test # git rev-parse -q --verify 99f070b62322a4b8c1252952735806d09eb44b68^{commit} 99f070b62322a4b8c1252952735806d09eb44b68 # git checkout -q -f -B kisskb 99f070b62322a4b8c1252952735806d09eb44b68 # git clean -qxdf # < git log -1 # commit 99f070b62322a4b8c1252952735806d09eb44b68 # Author: Qian Cai <cai@redhat.com> # Date: Wed Oct 28 14:23:34 2020 -0400 # # powerpc/smp: Call rcu_cpu_starting() earlier # # The call to rcu_cpu_starting() in start_secondary() is not early # enough in the CPU-hotplug onlining process, which results in lockdep # splats as follows (with CONFIG_PROVE_RCU_LIST=y): # # WARNING: suspicious RCU usage # ----------------------------- # kernel/locking/lockdep.c:3497 RCU-list traversed in non-reader section!! # # other info that might help us debug this: # # RCU used illegally from offline CPU! # rcu_scheduler_active = 1, debug_locks = 1 # no locks held by swapper/1/0. # # Call Trace: # dump_stack+0xec/0x144 (unreliable) # lockdep_rcu_suspicious+0x128/0x14c # __lock_acquire+0x1060/0x1c60 # lock_acquire+0x140/0x5f0 # _raw_spin_lock_irqsave+0x64/0xb0 # clockevents_register_device+0x74/0x270 # register_decrementer_clockevent+0x94/0x110 # start_secondary+0x134/0x800 # start_secondary_prolog+0x10/0x14 # # This is avoided by adding a call to rcu_cpu_starting() near the # beginning of the start_secondary() function. Note that the # raw_smp_processor_id() is required in order to avoid calling into # lockdep before RCU has declared the CPU to be watched for readers. # # It's safe to call rcu_cpu_starting() in the arch code as well as later # in generic code, as explained by Paul: # # It uses a per-CPU variable so that RCU pays attention only to the # first call to rcu_cpu_starting() if there is more than one of them. # This is even intentional, due to there being a generic # arch-independent call to rcu_cpu_starting() in # notify_cpu_starting(). # # So multiple calls to rcu_cpu_starting() are fine by design. # # Fixes: 4d004099a668 ("lockdep: Fix lockdep recursion") # Signed-off-by: Qian Cai <cai@redhat.com> # Acked-by: Paul E. McKenney <paulmck@kernel.org> # [mpe: Add Fixes tag, reword slightly & expand change log] # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # Link: https://lore.kernel.org/r/20201028182334.13466-1-cai@redhat.com # < /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 99f070b62322a4b8c1252952735806d09eb44b68 # < make -s -j 80 ARCH=arm64 O=/kisskb/build/powerpc-fixes_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- defconfig # < make -s -j 80 ARCH=arm64 O=/kisskb/build/powerpc-fixes_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- help # make -s -j 80 ARCH=arm64 O=/kisskb/build/powerpc-fixes_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- olddefconfig # make -s -j 80 ARCH=arm64 O=/kisskb/build/powerpc-fixes_arm64-defconfig_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:37: LSE atomics not supported by binutils /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) /kisskb/src/arch/arm64/boot/dts/qcom/ipq6018.dtsi:185.3-14: Warning (dma_ranges_format): /soc:dma-ranges: empty "dma-ranges" property but its #address-cells (1) differs from / (2) /kisskb/src/arch/arm64/boot/dts/qcom/ipq6018.dtsi:185.3-14: Warning (dma_ranges_format): /soc:dma-ranges: empty "dma-ranges" property but its #size-cells (1) differs from / (2) Completed OK # rm -rf /kisskb/build/powerpc-fixes_arm64-defconfig_arm64-gcc5.4 # Build took: 0:06:11.484420

© Michael Ellerman 2006-2018.