From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [sashal-linux-stable:queue-4.4 22/34] WARNING: vmlinux.o(.text+0x4efdf8): Section mismatch in reference from the function pxm_to_node() to the variable .init.data:numa_off
Date: Tue, 03 Nov 2020 17:00:01 +0800 [thread overview]
Message-ID: <202011031658.aPzLOGqf-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git queue-4.4
head: c3c449fe8b08850b9146f83fad26701575cfd387
commit: 8603591e9f729fc0ec7a91664ee068931c6fb01a [22/34] ACPI: Add out of bounds and numa_off protections to pxm_to_node()
config: x86_64-randconfig-a012-20201102 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git/commit/?id=8603591e9f729fc0ec7a91664ee068931c6fb01a
git remote add sashal-linux-stable https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
git fetch --no-tags sashal-linux-stable queue-4.4
git checkout 8603591e9f729fc0ec7a91664ee068931c6fb01a
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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 >>):
>> WARNING: vmlinux.o(.text+0x4efdf8): Section mismatch in reference from the function pxm_to_node() to the variable .init.data:numa_off
The function pxm_to_node() references
the variable __initdata numa_off.
This is often because pxm_to_node lacks a __initdata
annotation or the annotation of numa_off is wrong.
---
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: 24126 bytes --]
reply other threads:[~2020-11-03 9:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202011031658.aPzLOGqf-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.