[peterz-queue:locking/core 21/21] WARNING: modpost: vmlinux.o(.text.unlikely+0x253ac): Section mismatch in reference from the function __set_bit() to the variable .init.data:initcall_level_names

* [peterz-queue:locking/core 21/21] WARNING: modpost: vmlinux.o(.text.unlikely+0x253ac): Section mismatch in reference from the function __set_bit() to the variable .init.data:initcall_level_names
@ 2021-07-14  1:08 ` kernel test robot
  0 siblings, 0 replies; 4+ messages in thread
From: kernel test robot @ 2021-07-14  1:08 UTC (permalink / raw)
  To: Mark Rutland; +Cc: kbuild-all, linux-kernel, Peter Zijlstra

[-- Attachment #1: Type: text/plain, Size: 2620 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
head:   ceb71d863ae0bfca14303c189bbf5903a02ff95a
commit: ceb71d863ae0bfca14303c189bbf5903a02ff95a [21/21] locking/atomic: add generic arch_*() bitops
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=ceb71d863ae0bfca14303c189bbf5903a02ff95a
        git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
        git fetch --no-tags peterz-queue locking/core
        git checkout ceb71d863ae0bfca14303c189bbf5903a02ff95a
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross O=build_dir ARCH=xtensa SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>, old ones prefixed by <<):

>> WARNING: modpost: vmlinux.o(.text.unlikely+0x253ac): Section mismatch in reference from the function __set_bit() to the variable .init.data:initcall_level_names
The function __set_bit() references
the variable __initdata initcall_level_names.
This is often because __set_bit lacks a __initdata
annotation or the annotation of initcall_level_names is wrong.

The below error/warnings are from parent commit:
<< WARNING: modpost: vmlinux.o(.text.unlikely+0x24a10): Section mismatch in reference from the function bfq_pos_tree_add_move() to the variable .init.data:initcall_level_names
<< WARNING: modpost: vmlinux.o(.text.unlikely+0x24f84): Section mismatch in reference from the function bitmap_equal() to the variable .init.rodata:__setup_str_initcall_blacklist
<< WARNING: modpost: vmlinux.o(.data+0x15ebc68): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:__setup_str_initcall_blacklist
<< WARNING: modpost: vmlinux.o(.data+0x15f67f0): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:__setup_str_initcall_blacklist
<< WARNING: modpost: vmlinux.o(.data+0x15ebb70): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:__setup_str_initcall_blacklist

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 67906 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread