Re: locking/lockdep: Fix NMI handling
From: kbuild test robot
Date: Mon Sep 10 2018 - 01:39:58 EST
Hi Peter,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/locking/core]
[also build test ERROR on v4.19-rc2 next-20180906]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Peter-Zijlstra/locking-lockdep-Fix-NMI-handling/20180910-124306
config: i386-randconfig-x009-09101226 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from include/linux/spinlock_types.h:18:0,
from kernel/bounds.c:14:
include/linux/lockdep.h: In function 'lockdep_off':
>> include/linux/lockdep.h:277:2: error: 'current' undeclared (first use in this function)
current->lockdep_recursion++;
^~~~~~~
include/linux/lockdep.h:277:2: note: each undeclared identifier is reported only once for each function it appears in
include/linux/lockdep.h: In function 'lockdep_on':
include/linux/lockdep.h:282:2: error: 'current' undeclared (first use in this function)
current->lockdep_recursion--;
^~~~~~~
make[2]: *** [kernel/bounds.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [sub-make] Error 2
vim +/current +277 include/linux/lockdep.h
274
275 static inline void lockdep_off(void)
276 {
> 277 current->lockdep_recursion++;
278 }
279
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Attachment:
.config.gz
Description: application/gzip