tree: https://github.com/hnaz/linux-mm master head: 5d9ee416b5701096536c7a63c04dbe25012baa9e commit: 76e15e67350bfb1e0b1b151255c1d0b075143424 [95/340] mm: return faster for non-fatal signals in user mode faults config: mips-allyesconfig (attached as .config) compiler: mips-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 76e15e67350bfb1e0b1b151255c1d0b075143424 # save the attached .config to linux build tree GCC_VERSION=9.2.0 make.cross ARCH=mips 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/linux/init.h:5, from sound/core/hwdep.c:8: include/linux/sched/signal.h: In function 'fault_signal_pending': >> include/linux/sched/signal.h:383:6: error: implicit declaration of function 'user_mode'; did you mean 'user_sd'? [-Werror=implicit-function-declaration] 383 | (user_mode(regs) && signal_pending(current)))); | ^~~~~~~~~ include/linux/compiler.h:78:42: note: in definition of macro 'unlikely' 78 | # define unlikely(x) __builtin_expect(!!(x), 0) | ^ cc1: some warnings being treated as errors vim +383 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 (user_mode(regs) && signal_pending(current)))); 384 } 385 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@xxxxxxxxxxxx
Attachment:
.config.gz
Description: application/gzip
