[rcu:dev.2020.05.14c 52/67] ld.lld: error: section .text at 0xFFFFFFFF84000000 of size 0xF85B74 exceeds available address space
by kbuild test robot
CC: linux-kernel(a)vger.kernel.org
TO: "Joel Fernandes (Google)" <joel(a)joelfernandes.org>
CC: "Paul E. McKenney" <paulmck(a)kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.05.14c
head: 53281c92e73ab42f7dec96595dec2476fa8d0a34
commit: 0e94d87bed082e69ef1daf0684468e2abaec5d70 [52/67] rcu/tree: Remove dynticks_nmi_nesting counter
config: mips-randconfig-r004-20200517 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 13d44b2a0c7ef404b13b16644765977cd5310fe2)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
git checkout 0e94d87bed082e69ef1daf0684468e2abaec5d70
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ld.lld: error: section .text at 0xFFFFFFFF84000000 of size 0xF85B74 exceeds available address space
>> ld.lld: error: section __ex_table at 0xFFFFFFFF84F85B80 of size 0x1DE8 exceeds available address space
>> ld.lld: error: section __dbe_table at 0xFFFFFFFF84F87968 of size 0x0 exceeds available address space
>> ld.lld: error: section .rodata at 0xFFFFFFFF84F88000 of size 0x216AF7 exceeds available address space
ld.lld: error: section .data..page_aligned at 0xFFFFFFFF8519F000 of size 0x2000 exceeds available address space
ld.lld: error: section .got at 0xFFFFFFFF851A1000 of size 0x8 exceeds available address space
ld.lld: error: section .rodata1 at 0xFFFFFFFF851A1008 of size 0x0 exceeds available address space
ld.lld: error: section .pci_fixup at 0xFFFFFFFF851A1008 of size 0x1E80 exceeds available address space
ld.lld: error: section .builtin_fw at 0xFFFFFFFF851A2E88 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab at 0xFFFFFFFF851A2E88 of size 0x10350 exceeds available address space
ld.lld: error: section __ksymtab_gpl at 0xFFFFFFFF851B31D8 of size 0xEF58 exceeds available address space
ld.lld: error: section __ksymtab_unused at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab_unused_gpl at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab_gpl_future at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_gpl at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused_gpl at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_gpl_future at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab_strings at 0xFFFFFFFF851C2130 of size 0x34374 exceeds available address space
ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years, 4 months
[block:for-5.8/block 71/79] ld.lld: error: section .text at 0xFFFFFFFF84000000 of size 0xF83C94 exceeds available address space
by kbuild test robot
TO: Ming Lei <ming.lei(a)redhat.com>
CC: Jens Axboe <axboe(a)kernel.dk>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-5.8/block
head: 870c153cf0e6df1b8b5226af41b19945e8e0d143
commit: 71ac860af824ce9ebbbe8de20044e777c0fc33b9 [71/79] block: move blk_io_schedule() out of header file
config: mips-randconfig-r004-20200517 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 13d44b2a0c7ef404b13b16644765977cd5310fe2)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
git checkout 71ac860af824ce9ebbbe8de20044e777c0fc33b9
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ld.lld: error: section .text at 0xFFFFFFFF84000000 of size 0xF83C94 exceeds available address space
>> ld.lld: error: section __ex_table at 0xFFFFFFFF84F83CA0 of size 0x1DE8 exceeds available address space
>> ld.lld: error: section __dbe_table at 0xFFFFFFFF84F85A88 of size 0x0 exceeds available address space
ld.lld: error: section .rodata at 0xFFFFFFFF84F86000 of size 0x21658F exceeds available address space
ld.lld: error: section .data..page_aligned at 0xFFFFFFFF8519D000 of size 0x2000 exceeds available address space
ld.lld: error: section .got at 0xFFFFFFFF8519F000 of size 0x8 exceeds available address space
ld.lld: error: section .rodata1 at 0xFFFFFFFF8519F008 of size 0x0 exceeds available address space
ld.lld: error: section .pci_fixup at 0xFFFFFFFF8519F008 of size 0x1E80 exceeds available address space
ld.lld: error: section .builtin_fw at 0xFFFFFFFF851A0E88 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab at 0xFFFFFFFF851A0E88 of size 0x10338 exceeds available address space
>> ld.lld: error: section __ksymtab_gpl at 0xFFFFFFFF851B11C0 of size 0xEF10 exceeds available address space
>> ld.lld: error: section __ksymtab_unused at 0xFFFFFFFF851C00D0 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab_unused_gpl at 0xFFFFFFFF851C00D0 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab_gpl_future at 0xFFFFFFFF851C00D0 of size 0x0 exceeds available address space
>> ld.lld: error: section __kcrctab at 0xFFFFFFFF851C00D0 of size 0x0 exceeds available address space
>> ld.lld: error: section __kcrctab_gpl at 0xFFFFFFFF851C00D0 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused at 0xFFFFFFFF851C00D0 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused_gpl at 0xFFFFFFFF851C00D0 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_gpl_future at 0xFFFFFFFF851C00D0 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab_strings at 0xFFFFFFFF851C00D0 of size 0x342CC exceeds available address space
ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years, 4 months
[rcu:tglx.2020.05.15a 8/17] ld.lld: error: section __ksymtab_gpl at 0xFFFFFFFF851B41D0 of size 0xEFB8 exceeds available address space
by kbuild test robot
CC: linux-kernel(a)vger.kernel.org
TO: Peter Zijlstra <peterz(a)infradead.org>
CC: Thomas Gleixner <tglx(a)linutronix.de>
CC: Alexandre Chartre <alexandre.chartre(a)oracle.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tglx.2020.05.15a
head: 0adeeee7dd32b29e2f0d911a48aeac05475766fc
commit: 9f991ea52ab22f7f16dbcf2a7df1e1a926fd88ce [8/17] lockdep: Always inline lockdep_{off,on}()
config: mips-randconfig-r004-20200517 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 13d44b2a0c7ef404b13b16644765977cd5310fe2)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
git checkout 9f991ea52ab22f7f16dbcf2a7df1e1a926fd88ce
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
ld.lld: error: section .text at 0xFFFFFFFF84000000 of size 0xF86E8C exceeds available address space
ld.lld: error: section __ex_table at 0xFFFFFFFF84F86E90 of size 0x1DE8 exceeds available address space
ld.lld: error: section __dbe_table at 0xFFFFFFFF84F88C78 of size 0x0 exceeds available address space
ld.lld: error: section .rodata at 0xFFFFFFFF84F89000 of size 0x216B5F exceeds available address space
ld.lld: error: section .data..page_aligned at 0xFFFFFFFF851A0000 of size 0x2000 exceeds available address space
ld.lld: error: section .got at 0xFFFFFFFF851A2000 of size 0x8 exceeds available address space
ld.lld: error: section .rodata1 at 0xFFFFFFFF851A2008 of size 0x0 exceeds available address space
ld.lld: error: section .pci_fixup at 0xFFFFFFFF851A2008 of size 0x1E90 exceeds available address space
ld.lld: error: section .builtin_fw at 0xFFFFFFFF851A3E98 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab at 0xFFFFFFFF851A3E98 of size 0x10338 exceeds available address space
>> ld.lld: error: section __ksymtab_gpl at 0xFFFFFFFF851B41D0 of size 0xEFB8 exceeds available address space
>> ld.lld: error: section __ksymtab_unused at 0xFFFFFFFF851C3188 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab_unused_gpl at 0xFFFFFFFF851C3188 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab_gpl_future at 0xFFFFFFFF851C3188 of size 0x0 exceeds available address space
>> ld.lld: error: section __kcrctab at 0xFFFFFFFF851C3188 of size 0x0 exceeds available address space
>> ld.lld: error: section __kcrctab_gpl at 0xFFFFFFFF851C3188 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused at 0xFFFFFFFF851C3188 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused_gpl at 0xFFFFFFFF851C3188 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_gpl_future at 0xFFFFFFFF851C3188 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab_strings at 0xFFFFFFFF851C3188 of size 0x343F8 exceeds available address space
ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years, 4 months
[linux-stable-rc:linux-5.4.y 4356/5111] include/linux/rcupdate.h:651:9: sparse: sparse: too many warnings
by kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
head: ed1728340b22cd2d0143fcc832c76ac40f409888
commit: 5f2d04139aa5ed04eab54b84e8a25bab87a2449c [4356/5111] signal: Extend exec_id to 64bits
config: s390-randconfig-s002-20200517 (attached as .config)
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-193-gb8fad4bc-dirty
git checkout 5f2d04139aa5ed04eab54b84e8a25bab87a2449c
# save the attached .config to linux build tree
make C=1 ARCH=s390 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
sparse warnings: (new ones prefixed by >>)
kernel/signal.c:2030:24: sparse: expected struct task_struct *parent
kernel/signal.c:2030:24: sparse: got struct task_struct [noderef] <asn:4> *real_parent
kernel/signal.c:2511:52: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct task_struct *tsk @@ got struct task_structstruct task_struct *tsk @@
kernel/signal.c:2511:52: sparse: expected struct task_struct *tsk
kernel/signal.c:2511:52: sparse: got struct task_struct [noderef] <asn:4> *parent
kernel/signal.c:2513:49: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile *p @@ got struct cred const [noderef] <asn:4>void const volatile *p @@
kernel/signal.c:2513:49: sparse: expected void const volatile *p
kernel/signal.c:2513:49: sparse: got struct cred const [noderef] <asn:4> *[noderef] <asn:4> *
kernel/signal.c:2513:49: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile *p @@ got struct cred const [noderef] <asn:4>void const volatile *p @@
kernel/signal.c:2513:49: sparse: expected void const volatile *p
kernel/signal.c:2513:49: sparse: got struct cred const [noderef] <asn:4> *[noderef] <asn:4> *
kernel/signal.c:3015:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3015:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3015:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3015:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3046:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3046:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3046:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3046:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3087:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3087:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3103:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3103:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3495:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3495:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3495:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3495:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3495:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3495:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3528:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3528:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3528:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3528:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3528:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3528:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3561:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3561:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3561:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3561:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3561:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3561:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3592:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3592:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3592:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3592:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3592:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3592:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3681:46: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct siginfo const [noderef] [usertype] <asn:1> *from @@ got deref] [usertype] <asn:1> *from @@
kernel/signal.c:3681:46: sparse: expected struct siginfo const [noderef] [usertype] <asn:1> *from
kernel/signal.c:3681:46: sparse: got struct siginfo [usertype] *info
kernel/signal.c:3713:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3713:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3863:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3863:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3874:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3874:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3903:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3903:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3914:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:3914:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4042:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4042:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4042:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4042:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4110:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4110:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4110:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4110:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4146:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4146:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4162:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4162:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4185:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4185:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4185:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4185:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4233:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4233:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4233:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4233:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4258:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4258:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4258:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4258:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4305:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4305:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4305:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4305:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4341:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4341:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4341:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4341:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4409:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4409:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4456:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4456:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4470:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:4470:1: sparse: sparse: Using plain integer as NULL pointer
kernel/signal.c:1294:9: sparse: sparse: context imbalance in 'do_send_sig_info' - different lock contexts for basic block
include/linux/rcupdate.h:649:9: sparse: sparse: context imbalance in '__lock_task_sighand' - different lock contexts for basic block
>> include/linux/rcupdate.h:651:9: sparse: sparse: too many warnings
vim +651 include/linux/rcupdate.h
^1da177e4c3f41 Linus Torvalds 2005-04-16 603
^1da177e4c3f41 Linus Torvalds 2005-04-16 604 /*
^1da177e4c3f41 Linus Torvalds 2005-04-16 605 * So where is rcu_write_lock()? It does not exist, as there is no
^1da177e4c3f41 Linus Torvalds 2005-04-16 606 * way for writers to lock out RCU readers. This is a feature, not
^1da177e4c3f41 Linus Torvalds 2005-04-16 607 * a bug -- this property is what provides RCU's performance benefits.
^1da177e4c3f41 Linus Torvalds 2005-04-16 608 * Of course, writers must coordinate with each other. The normal
^1da177e4c3f41 Linus Torvalds 2005-04-16 609 * spinlock primitives work well for this, but any other technique may be
^1da177e4c3f41 Linus Torvalds 2005-04-16 610 * used as well. RCU does not care how the writers keep out of each
^1da177e4c3f41 Linus Torvalds 2005-04-16 611 * others' way, as long as they do so.
^1da177e4c3f41 Linus Torvalds 2005-04-16 612 */
3d76c082907e8f Paul E. McKenney 2009-09-28 613
3d76c082907e8f Paul E. McKenney 2009-09-28 614 /**
ca5ecddfa8fcbd Paul E. McKenney 2010-04-28 615 * rcu_read_unlock() - marks the end of an RCU read-side critical section.
3d76c082907e8f Paul E. McKenney 2009-09-28 616 *
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 617 * In most situations, rcu_read_unlock() is immune from deadlock.
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 618 * However, in kernels built with CONFIG_RCU_BOOST, rcu_read_unlock()
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 619 * is responsible for deboosting, which it does via rt_mutex_unlock().
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 620 * Unfortunately, this function acquires the scheduler's runqueue and
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 621 * priority-inheritance spinlocks. This means that deadlock could result
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 622 * if the caller of rcu_read_unlock() already holds one of these locks or
ec84b27f9b3b56 Anna-Maria Gleixner 2018-05-25 623 * any lock that is ever acquired while holding them.
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 624 *
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 625 * That said, RCU readers are never priority boosted unless they were
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 626 * preempted. Therefore, one way to avoid deadlock is to make sure
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 627 * that preemption never happens within any RCU read-side critical
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 628 * section whose outermost rcu_read_unlock() is called with one of
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 629 * rt_mutex_unlock()'s locks held. Such preemption can be avoided in
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 630 * a number of ways, for example, by invoking preempt_disable() before
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 631 * critical section's outermost rcu_read_lock().
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 632 *
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 633 * Given that the set of locks acquired by rt_mutex_unlock() might change
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 634 * at any time, a somewhat more future-proofed approach is to make sure
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 635 * that that preemption never happens within any RCU read-side critical
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 636 * section whose outermost rcu_read_unlock() is called with irqs disabled.
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 637 * This approach relies on the fact that rt_mutex_unlock() currently only
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 638 * acquires irq-disabled locks.
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 639 *
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 640 * The second of these two approaches is best in most situations,
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 641 * however, the first approach can also be useful, at least to those
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 642 * developers willing to keep abreast of the set of locks acquired by
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 643 * rt_mutex_unlock().
f27bc4873fa8b7 Paul E. McKenney 2014-05-04 644 *
3d76c082907e8f Paul E. McKenney 2009-09-28 645 * See rcu_read_lock() for more information.
3d76c082907e8f Paul E. McKenney 2009-09-28 646 */
bc33f24bdca8b6 Paul E. McKenney 2009-08-22 647 static inline void rcu_read_unlock(void)
bc33f24bdca8b6 Paul E. McKenney 2009-08-22 648 {
f78f5b90c4ffa5 Paul E. McKenney 2015-06-18 649 RCU_LOCKDEP_WARN(!rcu_is_watching(),
bde23c6892878e Heiko Carstens 2012-02-01 650 "rcu_read_unlock() used illegally while idle");
bc33f24bdca8b6 Paul E. McKenney 2009-08-22 @651 __release(RCU);
bc33f24bdca8b6 Paul E. McKenney 2009-08-22 652 __rcu_read_unlock();
d24209bb689e2c Paul E. McKenney 2015-01-21 653 rcu_lock_release(&rcu_lock_map); /* Keep acq info for rls diags. */
bc33f24bdca8b6 Paul E. McKenney 2009-08-22 654 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 655
:::::: The code at line 651 was first introduced by commit
:::::: bc33f24bdca8b6e97376e3a182ab69e6cdefa989 rcu: Consolidate sparse and lockdep declarations in include/linux/rcupdate.h
:::::: TO: Paul E. McKenney <paulmck(a)linux.vnet.ibm.com>
:::::: CC: Ingo Molnar <mingo(a)elte.hu>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years, 4 months
[rcu:dev.2020.05.14c 20/67] ld.lld: error: section __ksymtab_unused at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
by kbuild test robot
CC: linux-kernel(a)vger.kernel.org
TO: "Paul E. McKenney" <paulmck(a)kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.05.14c
head: 53281c92e73ab42f7dec96595dec2476fa8d0a34
commit: f736e0f1a55a88cb258b73da77463573739e9ac9 [20/67] Merge branches 'fixes.2020.04.27a', 'kfree_rcu.2020.04.27a', 'rcu-tasks.2020.04.27a', 'stall.2020.04.27a' and 'torture.2020.05.07a' into HEAD
config: mips-randconfig-r004-20200517 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 13d44b2a0c7ef404b13b16644765977cd5310fe2)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
git checkout f736e0f1a55a88cb258b73da77463573739e9ac9
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
ld.lld: error: section .text at 0xFFFFFFFF84000000 of size 0xF85DF4 exceeds available address space
ld.lld: error: section __ex_table at 0xFFFFFFFF84F85E00 of size 0x1DE8 exceeds available address space
ld.lld: error: section __dbe_table at 0xFFFFFFFF84F87BE8 of size 0x0 exceeds available address space
ld.lld: error: section .rodata at 0xFFFFFFFF84F88000 of size 0x216AFF exceeds available address space
ld.lld: error: section .data..page_aligned at 0xFFFFFFFF8519F000 of size 0x2000 exceeds available address space
ld.lld: error: section .got at 0xFFFFFFFF851A1000 of size 0x8 exceeds available address space
ld.lld: error: section .rodata1 at 0xFFFFFFFF851A1008 of size 0x0 exceeds available address space
ld.lld: error: section .pci_fixup at 0xFFFFFFFF851A1008 of size 0x1E80 exceeds available address space
ld.lld: error: section .builtin_fw at 0xFFFFFFFF851A2E88 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab at 0xFFFFFFFF851A2E88 of size 0x10350 exceeds available address space
>> ld.lld: error: section __ksymtab_gpl at 0xFFFFFFFF851B31D8 of size 0xEF58 exceeds available address space
>> ld.lld: error: section __ksymtab_unused at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab_unused_gpl at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab_gpl_future at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
>> ld.lld: error: section __kcrctab at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
>> ld.lld: error: section __kcrctab_gpl at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused_gpl at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_gpl_future at 0xFFFFFFFF851C2130 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab_strings at 0xFFFFFFFF851C2130 of size 0x34374 exceeds available address space
ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years, 4 months
[sashal-linux-stable:queue-4.9 54/58] drivers/pinctrl/intel/pinctrl-baytrail.c:1506:2: error: unknown field 'set_config' specified in initializer
by kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git queue-4.9
head: df412d9853e7e0696afb737e447a5e94947e82ca
commit: 46c51db24e60f839498b5de1553a9ab82f68240e [54/58] pinctrl: baytrail: Enable pin configuration setting for GPIO chip
config: x86_64-randconfig-a002-20200517 (attached as .config)
compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
reproduce:
git checkout 46c51db24e60f839498b5de1553a9ab82f68240e
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/pinctrl/intel/pinctrl-baytrail.c:1506:2: error: unknown field 'set_config' specified in initializer
.set_config = gpiochip_generic_config,
^
drivers/pinctrl/intel/pinctrl-baytrail.c:1506:17: error: 'gpiochip_generic_config' undeclared here (not in a function)
.set_config = gpiochip_generic_config,
^
vim +/set_config +1506 drivers/pinctrl/intel/pinctrl-baytrail.c
1496
1497 static const struct gpio_chip byt_gpio_chip = {
1498 .owner = THIS_MODULE,
1499 .request = gpiochip_generic_request,
1500 .free = gpiochip_generic_free,
1501 .get_direction = byt_gpio_get_direction,
1502 .direction_input = byt_gpio_direction_input,
1503 .direction_output = byt_gpio_direction_output,
1504 .get = byt_gpio_get,
1505 .set = byt_gpio_set,
> 1506 .set_config = gpiochip_generic_config,
1507 .dbg_show = byt_gpio_dbg_show,
1508 };
1509
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years, 4 months
[sashal-linux-stable:queue-4.9 54/58] drivers/pinctrl/intel/pinctrl-baytrail.c:1506:3: error: 'const struct gpio_chip' has no member named 'set_config'
by kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git queue-4.9
head: df412d9853e7e0696afb737e447a5e94947e82ca
commit: 46c51db24e60f839498b5de1553a9ab82f68240e [54/58] pinctrl: baytrail: Enable pin configuration setting for GPIO chip
config: x86_64-randconfig-a003-20200517 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
git checkout 46c51db24e60f839498b5de1553a9ab82f68240e
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/pinctrl/intel/pinctrl-baytrail.c:1506:3: error: 'const struct gpio_chip' has no member named 'set_config'
.set_config = gpiochip_generic_config,
^~~~~~~~~~
>> drivers/pinctrl/intel/pinctrl-baytrail.c:1506:17: error: 'gpiochip_generic_config' undeclared here (not in a function); did you mean 'gpiochip_generic_free'?
.set_config = gpiochip_generic_config,
^~~~~~~~~~~~~~~~~~~~~~~
gpiochip_generic_free
vim +1506 drivers/pinctrl/intel/pinctrl-baytrail.c
1496
1497 static const struct gpio_chip byt_gpio_chip = {
1498 .owner = THIS_MODULE,
1499 .request = gpiochip_generic_request,
1500 .free = gpiochip_generic_free,
1501 .get_direction = byt_gpio_get_direction,
1502 .direction_input = byt_gpio_direction_input,
1503 .direction_output = byt_gpio_direction_output,
1504 .get = byt_gpio_get,
1505 .set = byt_gpio_set,
> 1506 .set_config = gpiochip_generic_config,
1507 .dbg_show = byt_gpio_dbg_show,
1508 };
1509
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years, 4 months
[rcu:tglx.2020.05.15a 3/17] ld.lld: error: section .data..page_aligned at 0xFFFFFFFF851A0000 of size 0x2000 exceeds available address space
by kbuild test robot
CC: linux-kernel(a)vger.kernel.org
TO: Thomas Gleixner <tglx(a)linutronix.de>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tglx.2020.05.15a
head: 0adeeee7dd32b29e2f0d911a48aeac05475766fc
commit: 184655d0a79ee1b4edf32468221ec3ccd25e3584 [3/17] Merge tag 'noinstr-lds-2020-05-15' into core/nmi
config: mips-randconfig-r004-20200517 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 13d44b2a0c7ef404b13b16644765977cd5310fe2)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
git checkout 184655d0a79ee1b4edf32468221ec3ccd25e3584
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
ld.lld: error: section .text at 0xFFFFFFFF84000000 of size 0xF86E5C exceeds available address space
ld.lld: error: section __ex_table at 0xFFFFFFFF84F86E60 of size 0x1DE8 exceeds available address space
ld.lld: error: section __dbe_table at 0xFFFFFFFF84F88C48 of size 0x0 exceeds available address space
ld.lld: error: section .rodata at 0xFFFFFFFF84F89000 of size 0x216B5F exceeds available address space
>> ld.lld: error: section .data..page_aligned at 0xFFFFFFFF851A0000 of size 0x2000 exceeds available address space
>> ld.lld: error: section .got at 0xFFFFFFFF851A2000 of size 0x8 exceeds available address space
>> ld.lld: error: section .rodata1 at 0xFFFFFFFF851A2008 of size 0x0 exceeds available address space
>> ld.lld: error: section .pci_fixup at 0xFFFFFFFF851A2008 of size 0x1E90 exceeds available address space
>> ld.lld: error: section .builtin_fw at 0xFFFFFFFF851A3E98 of size 0x0 exceeds available address space
>> ld.lld: error: section __ksymtab at 0xFFFFFFFF851A3E98 of size 0x10350 exceeds available address space
ld.lld: error: section __ksymtab_gpl at 0xFFFFFFFF851B41E8 of size 0xEFB8 exceeds available address space
ld.lld: error: section __ksymtab_unused at 0xFFFFFFFF851C31A0 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab_unused_gpl at 0xFFFFFFFF851C31A0 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab_gpl_future at 0xFFFFFFFF851C31A0 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab at 0xFFFFFFFF851C31A0 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_gpl at 0xFFFFFFFF851C31A0 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused at 0xFFFFFFFF851C31A0 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_unused_gpl at 0xFFFFFFFF851C31A0 of size 0x0 exceeds available address space
ld.lld: error: section __kcrctab_gpl_future at 0xFFFFFFFF851C31A0 of size 0x0 exceeds available address space
ld.lld: error: section __ksymtab_strings at 0xFFFFFFFF851C31A0 of size 0x3440F exceeds available address space
ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years, 4 months
arch/x86/kernel/apm_32.c:428:43: sparse: sparse: cast truncates bits from constant value (40000400 becomes 400)
by kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3d1c1e5931ce45b3a3f309385bbc00c78e9951c6
commit: 1651e700664b4597ddf4f8adfe435252a0d11277 x86: Fix bitops.h warning with a moved cast
date: 9 weeks ago
config: i386-randconfig-s002-20200517 (attached as .config)
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-193-gb8fad4bc-dirty
git checkout 1651e700664b4597ddf4f8adfe435252a0d11277
# save the attached .config to linux build tree
make C=1 ARCH=i386 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
sparse warnings: (new ones prefixed by >>)
>> arch/x86/kernel/apm_32.c:428:43: sparse: sparse: cast truncates bits from constant value (40000400 becomes 400)
vim +428 arch/x86/kernel/apm_32.c
c7425314c755d5 arch/x86/kernel/apm_32.c Akinobu Mita 2009-08-09 421
c7425314c755d5 arch/x86/kernel/apm_32.c Akinobu Mita 2009-08-09 422 /*
c7425314c755d5 arch/x86/kernel/apm_32.c Akinobu Mita 2009-08-09 423 * Set up a segment that references the real mode segment 0x40
c7425314c755d5 arch/x86/kernel/apm_32.c Akinobu Mita 2009-08-09 424 * that extends up to the end of page zero (that we have reserved).
c7425314c755d5 arch/x86/kernel/apm_32.c Akinobu Mita 2009-08-09 425 * This is for buggy BIOS's that refer to (real mode) segment 0x40
c7425314c755d5 arch/x86/kernel/apm_32.c Akinobu Mita 2009-08-09 426 * even though they are called in protected mode.
c7425314c755d5 arch/x86/kernel/apm_32.c Akinobu Mita 2009-08-09 427 */
c7425314c755d5 arch/x86/kernel/apm_32.c Akinobu Mita 2009-08-09 @428 static struct desc_struct bad_bios_desc = GDT_ENTRY_INIT(0x4092,
c7425314c755d5 arch/x86/kernel/apm_32.c Akinobu Mita 2009-08-09 429 (unsigned long)__va(0x400UL), PAGE_SIZE - 0x400 - 1);
^1da177e4c3f41 arch/i386/kernel/apm.c Linus Torvalds 2005-04-16 430
:::::: The code at line 428 was first introduced by commit
:::::: c7425314c755d5f94da7c978205c85a7c6201212 x86: Introduce GDT_ENTRY_INIT(), initialize bad_bios_desc statically
:::::: TO: Akinobu Mita <akinobu.mita(a)gmail.com>
:::::: CC: Ingo Molnar <mingo(a)elte.hu>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
2 years, 4 months