Buildresult: powerpc-fixes/ppc64le_defconfig/powerpc-gcc5 built on Feb 5 2020, 01:44

kisskb

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

Status:	OK
Date/Time:	Feb 5 2020, 01:44
Duration:	0:03:17.444289
Builder:	blade46
Revision:	selftests/powerpc: Don't rely on segfault to rerun the test (`4399efc3f2f04ad8e6948461795de04ed1358402)`
Target:	powerpc-fixes/ppc64le_defconfig/powerpc-gcc5
Branch:	powerpc-fixes
Compiler:	powerpc-gcc5 (powerpc64-linux-gcc (GCC) 5.5.0 / GNU ld (GNU Binutils) 2.29.1.20170915)
Config:	ppc64le_defconfig (download)
Log:	Download original Possible warnings (3) WARNING: vmlinux.o(.text+0x31e4): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init() WARNING: vmlinux.o(.text+0x33c8): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() WARNING: 2 bad relocations Full Log # git rev-parse -q --verify 4399efc3f2f04ad8e6948461795de04ed1358402^{commit} 4399efc3f2f04ad8e6948461795de04ed1358402 already have revision, skipping fetch # git checkout -q -f -B kisskb 4399efc3f2f04ad8e6948461795de04ed1358402 # git clean -qxdf # < git log -1 # commit 4399efc3f2f04ad8e6948461795de04ed1358402 # Author: Gustavo Luiz Duarte <gustavold@linux.ibm.com> # Date: Mon Feb 3 13:09:06 2020 -0300 # # selftests/powerpc: Don't rely on segfault to rerun the test # # The test case tm-signal-context-force-tm expects a segfault to happen on # returning from signal handler, and then does a setcontext() to run the test # again. However, the test doesn't always segfault, causing the test to run a # single time. # # This patch fixes the test by putting it within a loop and jumping, via # setcontext, just prior to the loop in case it segfaults. This way we get the # desired behavior (run the test COUNT_MAX times) regardless if it segfaults or # not. This also reduces the use of setcontext for control flow logic, keeping it # only in the segfault handler. # # Also, since 'count' is changed within the signal handler, it is declared as # volatile to prevent any compiler optimization getting confused with # asynchronous changes. # # Signed-off-by: Gustavo Luiz Duarte <gustavold@linux.ibm.com> # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # Link: https://lore.kernel.org/r/20200203160906.24482-3-gustavold@linux.ibm.com # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld --version # < git log --format=%s --max-count=1 4399efc3f2f04ad8e6948461795de04ed1358402 # < make -s -j 32 ARCH=powerpc O=/kisskb/build/powerpc-fixes_ppc64le_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- ppc64le_defconfig # make -s -j 32 ARCH=powerpc O=/kisskb/build/powerpc-fixes_ppc64le_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- WARNING: vmlinux.o(.text+0x31e4): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init() The function __boot_from_prom() references the function __init prom_init(). This is often because __boot_from_prom lacks a __init annotation or the annotation of prom_init is wrong. WARNING: vmlinux.o(.text+0x33c8): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() The function start_here_common() references the function __init start_kernel(). This is often because start_here_common lacks a __init annotation or the annotation of start_kernel is wrong. WARNING: 2 bad relocations c000000001637178 R_PPC64_ADDR64 _binary__btf_vmlinux_bin_start c000000001637180 R_PPC64_ADDR64 _binary__btf_vmlinux_bin_end Completed OK # rm -rf /kisskb/build/powerpc-fixes_ppc64le_defconfig_ppc64le-gcc5 # Build took: 0:03:17.444289

© Michael Ellerman 2006-2018.