tree: https://github.com/hnaz/linux-mm master head: 5d9ee416b5701096536c7a63c04dbe25012baa9e commit: 133f884fbe299145671d583f255f71b63d9ad63f [89/340] mm: introduce fault_signal_pending() config: openrisc-randconfig-a001-20200309 (attached as .config) compiler: or1k-linux-gcc (GCC) 9.2.0 reproduce: wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross git checkout 133f884fbe299145671d583f255f71b63d9ad63f # save the attached .config to linux build tree GCC_VERSION=9.2.0 make.cross ARCH=openrisc If you fix the issue, kindly add following tag Reported-by: kbuild test robot <lkp@xxxxxxxxx> All errors (new ones prefixed by >>): In file included from include/asm-generic/bug.h:5, from ./arch/openrisc/include/generated/asm/bug.h:1, from include/linux/bug.h:5, from include/linux/signal.h:5, from arch/openrisc/kernel/asm-offsets.c:22: include/linux/sched/signal.h: In function 'fault_signal_pending': >> include/linux/sched/signal.h:381:33: error: 'VM_FAULT_RETRY' undeclared (first use in this function) 381 | return unlikely((fault_flags & VM_FAULT_RETRY) && | ^~~~~~~~~~~~~~ include/linux/compiler.h:78:42: note: in definition of macro 'unlikely' 78 | # define unlikely(x) __builtin_expect(!!(x), 0) | ^ include/linux/sched/signal.h:381:33: note: each undeclared identifier is reported only once for each function it appears in 381 | return unlikely((fault_flags & VM_FAULT_RETRY) && | ^~~~~~~~~~~~~~ include/linux/compiler.h:78:42: note: in definition of macro 'unlikely' 78 | # define unlikely(x) __builtin_expect(!!(x), 0) | ^ make[2]: *** [scripts/Makefile.build:101: arch/openrisc/kernel/asm-offsets.s] Error 1 make[2]: Target '__build' not remade because of errors. make[1]: *** [Makefile:1113: prepare0] Error 2 make[1]: Target 'prepare' not remade because of errors. make: *** [Makefile:180: sub-make] Error 2 26 real 6 user 11 sys 66.71% cpu make prepare vim +/VM_FAULT_RETRY +381 include/linux/sched/signal.h 371 372 /* 373 * This should only be used in fault handlers to decide whether we 374 * should stop the current fault routine to handle the signals 375 * instead, especially with the case where we've got interrupted with 376 * a VM_FAULT_RETRY. 377 */ 378 static inline bool fault_signal_pending(unsigned int fault_flags, 379 struct pt_regs *regs) 380 { > 381 return unlikely((fault_flags & VM_FAULT_RETRY) && 382 fatal_signal_pending(current)); 383 } 384 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@xxxxxxxxxxxx
Attachment:
.config.gz
Description: application/gzip
