From: kernel test robot <lkp@intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [hnaz-mm:master 34/291] WARNING: modpost: vmlinux.o(.data+0x234bc8): Section mismatch in reference from the variable fc2580_driver to the function .init.text:set_reset_devices()
Date: Sun, 24 Apr 2022 12:21:13 +0800 [thread overview]
Message-ID: <202204241241.dnUrBBvT-lkp@intel.com> (raw)
tree: https://github.com/hnaz/linux-mm master
head: ba42854fa9997614e0ffdbc35b082df3ba6e59da
commit: 477a4d0f1f38e738d1a50d5005b79aca719c30bc [34/291] mm/hugetlb: take src_mm->write_protect_seq in copy_hugetlb_page_range()
config: riscv-randconfig-r015-20220420 (https://download.01.org/0day-ci/archive/20220424/202204241241.dnUrBBvT-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project bac6cd5bf85669e3376610cfc4c4f9ca015e7b9b)
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
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://github.com/hnaz/linux-mm/commit/477a4d0f1f38e738d1a50d5005b79aca719c30bc
git remote add hnaz-mm https://github.com/hnaz/linux-mm
git fetch --no-tags hnaz-mm master
git checkout 477a4d0f1f38e738d1a50d5005b79aca719c30bc
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv 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(.data+0x234bc8): Section mismatch in reference from the variable fc2580_driver to the function .init.text:set_reset_devices()
The variable fc2580_driver references
the function __init set_reset_devices()
If the reference is valid then annotate the
variable with or __refdata (see linux/init.h) or name the variable:
Note: the below error/warnings can be found in parent commit:
<< WARNING: modpost: vmlinux.o(.text+0x13e3592): Section mismatch in reference from the function usbhid_find_interface() to the variable .init.text:.LBB0_1
<< WARNING: modpost: vmlinux.o(.text+0x13e3596): Section mismatch in reference from the function usbhid_find_interface() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.data+0x23ad30): Section mismatch in reference from the variable empty_map to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.data+0x258174): Section mismatch in reference from the variable w83795_in to the function .meminit.text:init_reserve_notifier()
<< WARNING: modpost: vmlinux.o(.data+0x258194): Section mismatch in reference from the variable w83795_in to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.data+0x23ba8c): Section mismatch in reference from the variable stm32_cec_driver to the variable .init.text:.LBB20_8
<< WARNING: modpost: vmlinux.o(.data+0x256558): Section mismatch in reference from the variable w83793_temp to the variable .init.text:.LBB46_1
<< WARNING: modpost: vmlinux.o(.data+0x25655c): Section mismatch in reference from the variable w83793_temp to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.data+0x230444): Section mismatch in reference from the variable ov5695_i2c_driver to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.data+0x25c1dc): Section mismatch in reference from the variable sensor_dev_attr_temp1_input to the function .meminit.text:init_reserve_notifier()
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-04-24 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 4:21 kernel test robot [this message]
2022-04-25 8:04 ` David Hildenbrand
2022-04-28 11:42 ` Chen, Rong A
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=202204241241.dnUrBBvT-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
/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