Buildresult: crypto/powernv_defconfig/powerpc-gcc5 built on Jan 9 2020, 15:34

kisskb

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

Status:	OK
Date/Time:	Jan 9 2020, 15:34
Duration:	0:06:16.913072
Builder:	ka1
Revision:	crypto: hisilicon/sec2 - Use atomics instead of __sync (`cb1eeb75cf3dd84ced81333967200583993dfd73)`
Target:	crypto/powernv_defconfig/powerpc-gcc5
Branch:	crypto
Compiler:	powerpc-gcc5 (powerpc64-linux-gcc (GCC) 5.5.0 / GNU ld (GNU Binutils) 2.29.1.20170915)
Config:	powernv_defconfig (download)
Log:	Download original Possible warnings (2) include/linux/kernel.h:37:33: warning: 'clone_src_i_size' may be used uninitialized in this function [-Wmaybe-uninitialized] WARNING: vmlinux.o(.text+0x2fc8): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() Full Log # git rev-parse -q --verify cb1eeb75cf3dd84ced81333967200583993dfd73^{commit} cb1eeb75cf3dd84ced81333967200583993dfd73 already have revision, skipping fetch # git checkout -q -f -B kisskb cb1eeb75cf3dd84ced81333967200583993dfd73 # git clean -qxdf # < git log -1 # commit cb1eeb75cf3dd84ced81333967200583993dfd73 # Author: Arnd Bergmann <arnd@arndb.de> # Date: Tue Jan 7 21:08:58 2020 +0100 # # crypto: hisilicon/sec2 - Use atomics instead of __sync # # The use of __sync functions for atomic memory access is not # supported in the kernel, and can result in a link error depending # on configuration: # # ERROR: "__tsan_atomic32_compare_exchange_strong" [drivers/crypto/hisilicon/sec2/hisi_sec2.ko] undefined! # ERROR: "__tsan_atomic64_fetch_add" [drivers/crypto/hisilicon/sec2/hisi_sec2.ko] undefined! # # Use the kernel's own atomic interfaces instead. This way the # debugfs interface actually reads the counter atomically. # # Fixes: 416d82204df4 ("crypto: hisilicon - add HiSilicon SEC V2 driver") # Signed-off-by: Arnd Bergmann <arnd@arndb.de> # Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> # < /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 cb1eeb75cf3dd84ced81333967200583993dfd73 # < make -s -j 8 ARCH=powerpc O=/kisskb/build/crypto_powernv_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- powernv_defconfig # make -s -j 8 ARCH=powerpc O=/kisskb/build/crypto_powernv_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- In file included from /kisskb/src/include/linux/list.h:9:0, from /kisskb/src/include/linux/wait.h:7, from /kisskb/src/include/linux/wait_bit.h:8, from /kisskb/src/include/linux/fs.h:6, from /kisskb/src/fs/btrfs/send.c:7: /kisskb/src/fs/btrfs/send.c: In function 'process_extent': /kisskb/src/include/linux/kernel.h:37:33: warning: 'clone_src_i_size' may be used uninitialized in this function [-Wmaybe-uninitialized] #define IS_ALIGNED(x, a) (((x) & ((typeof(x))(a) - 1)) == 0) ^ /kisskb/src/fs/btrfs/send.c:5088:6: note: 'clone_src_i_size' was declared here u64 clone_src_i_size; ^ WARNING: vmlinux.o(.text+0x2fc8): 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. Completed OK # rm -rf /kisskb/build/crypto_powernv_defconfig_ppc64le-gcc5 # Build took: 0:06:16.913072

© Michael Ellerman 2006-2018.