All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>
Subject: [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
Date: Wed, 14 Jul 2021 09:08:08 +0800	[thread overview]
Message-ID: <202107140904.leaDN2j0-lkp@intel.com> (raw)

[-- 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 --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [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
Date: Wed, 14 Jul 2021 09:08:08 +0800	[thread overview]
Message-ID: <202107140904.leaDN2j0-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2657 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 --]

             reply	other threads:[~2021-07-14  1:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14  1:08 kernel test robot [this message]
2021-07-14  1:08 ` [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 kernel test robot
2021-07-14 19:55 ` Mark Rutland
2021-07-14 19:55   ` Mark Rutland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202107140904.leaDN2j0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.