From: kernel test robot <lkp@intel.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Helge Deller <deller@gmx.de>
Subject: [linux-next:master 12563/12762] WARNING: modpost: vmlinux.o(.text+0xe0): Section mismatch in reference from the function __traceiter_gb_message_recv_response() to the function .init.text:memblock_alloc_try_nid()
Date: Fri, 21 Jan 2022 19:02:26 +0800 [thread overview]
Message-ID: <202201211840.tRDWmpre-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c94951012a748a0f8ed77cd8fc25640c6fe198f9
commit: 4f05e5a3946923676e147ad0e33c80df8249b2fe [12563/12762] parisc: Drop __init from map_pages declaration
config: parisc-buildonly-randconfig-r001-20220121 (https://download.01.org/0day-ci/archive/20220121/202201211840.tRDWmpre-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 11.2.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=4f05e5a3946923676e147ad0e33c80df8249b2fe
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 4f05e5a3946923676e147ad0e33c80df8249b2fe
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=parisc 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+0xe0): Section mismatch in reference from the function __traceiter_gb_message_recv_response() to the function .init.text:memblock_alloc_try_nid()
The function __traceiter_gb_message_recv_response() references
the function __init memblock_alloc_try_nid().
This is often because __traceiter_gb_message_recv_response lacks a __init
annotation or the annotation of memblock_alloc_try_nid is wrong.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-21 11:02 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=202201211840.tRDWmpre-lkp@intel.com \
--to=lkp@intel.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).