Messages in this thread | | | Date | Tue, 17 Jul 2018 09:44:51 +0800 | From | kbuild test robot <> | Subject | [rcu:dev 211/211] kernel/rcu/rcutorture.c:212:5: sparse: symbol 'err_segs_recorded' was not declared. Should it be static? |
| |
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev head: 07809ecaa895e92b00c28e8c0b7442bddb8a9324 commit: 07809ecaa895e92b00c28e8c0b7442bddb8a9324 [211/211] rcutorture: Dump reader protection sequence if failures or close calls reproduce: # apt-get install sparse git checkout 07809ecaa895e92b00c28e8c0b7442bddb8a9324 make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> kernel/rcu/rcutorture.c:212:5: sparse: symbol 'err_segs_recorded' was not declared. Should it be static? >> kernel/rcu/rcutorture.c:213:20: sparse: symbol 'err_segs' was not declared. Should it be static? >> kernel/rcu/rcutorture.c:214:5: sparse: symbol 'rt_read_nsegs' was not declared. Should it be static? include/linux/overflow.h:242:13: sparse: undefined identifier '__builtin_mul_overflow' include/linux/overflow.h:242:13: sparse: incorrect type in conditional include/linux/overflow.h:242:13: got void include/linux/overflow.h:244:13: sparse: undefined identifier '__builtin_mul_overflow' include/linux/overflow.h:244:13: sparse: incorrect type in conditional include/linux/overflow.h:244:13: got void include/linux/slab.h:631:13: sparse: undefined identifier '__builtin_mul_overflow' include/linux/slab.h:631:13: sparse: not a function <noident> include/linux/slab.h:631:13: sparse: not a function <noident> include/linux/slab.h:631:13: sparse: not a function <noident> include/linux/slab.h:631:13: sparse: not a function <noident> include/linux/overflow.h:242:13: sparse: call with no type! include/linux/overflow.h:244:13: sparse: call with no type! kernel/rcu/rcutorture.c:1183:9: sparse: context imbalance in 'rcutorture_one_extend' - different lock contexts for basic block include/linux/slab.h:631:13: sparse: call with no type!
Please review and possibly fold the followup patch.
--- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation
| |