From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 14111/14231] WARNING: modpost: vmlinux.o(.text.unlikely+0xce50): Section mismatch in reference from the function _ldm_printk() to the variable .init.data:initcall_level_names
Date: Thu, 22 Apr 2021 01:29:09 +0800 [thread overview]
Message-ID: <202104220104.FRLVIENW-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b74523885a715463203d4ccc3cf8c85952d3701a
commit: d03dff61231aedb1b2f889a3d1b3f5447d7b15c8 [14111/14231] lib: add fast path for find_next_*_bit()
config: xtensa-randconfig-r015-20210421 (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/next/linux-next.git/commit/?id=d03dff61231aedb1b2f889a3d1b3f5447d7b15c8
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout d03dff61231aedb1b2f889a3d1b3f5447d7b15c8
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=xtensa
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+0xce50): Section mismatch in reference from the function _ldm_printk() to the variable .init.data:initcall_level_names
The function _ldm_printk() references
the variable __initdata initcall_level_names.
This is often because _ldm_printk lacks a __initdata
annotation or the annotation of initcall_level_names is wrong.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for LOCKDEP
Depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT && (FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86)
Selected by
- LOCK_STAT && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
- DEBUG_LOCK_ALLOC && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 20425 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 14111/14231] WARNING: modpost: vmlinux.o(.text.unlikely+0xce50): Section mismatch in reference from the function _ldm_printk() to the variable .init.data:initcall_level_names
Date: Thu, 22 Apr 2021 01:29:09 +0800 [thread overview]
Message-ID: <202104220104.FRLVIENW-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2015 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b74523885a715463203d4ccc3cf8c85952d3701a
commit: d03dff61231aedb1b2f889a3d1b3f5447d7b15c8 [14111/14231] lib: add fast path for find_next_*_bit()
config: xtensa-randconfig-r015-20210421 (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/next/linux-next.git/commit/?id=d03dff61231aedb1b2f889a3d1b3f5447d7b15c8
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout d03dff61231aedb1b2f889a3d1b3f5447d7b15c8
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=xtensa
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+0xce50): Section mismatch in reference from the function _ldm_printk() to the variable .init.data:initcall_level_names
The function _ldm_printk() references
the variable __initdata initcall_level_names.
This is often because _ldm_printk lacks a __initdata
annotation or the annotation of initcall_level_names is wrong.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for LOCKDEP
Depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT && (FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86)
Selected by
- LOCK_STAT && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
- DEBUG_LOCK_ALLOC && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
---
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: 20425 bytes --]
next reply other threads:[~2021-04-21 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 17:29 kernel test robot [this message]
2021-04-21 17:29 ` [linux-next:master 14111/14231] WARNING: modpost: vmlinux.o(.text.unlikely+0xce50): Section mismatch in reference from the function _ldm_printk() to the variable .init.data:initcall_level_names kernel test robot
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=202104220104.FRLVIENW-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.