From: kernel test robot <lkp@intel.com>
To: "Steven Rostedt (Google)" <rostedt@goodmis.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: [ammarfaizi2-block:rostedt/linux-trace/merge-next-20220315 512/512] WARNING: modpost: vmlinux.o(.data+0x296750): Section mismatch in reference from the variable nft_rt_type to the function .init.text:set_reset_devices()
Date: Thu, 17 Mar 2022 21:59:31 +0800 [thread overview]
Message-ID: <202203172141.n0ep448q-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block rostedt/linux-trace/merge-next-20220315
head: 87a21b60077d8cb23d3e70a00a969b542d0695d8
commit: 87a21b60077d8cb23d3e70a00a969b542d0695d8 [512/512] Merge remote-tracking branch 'ftrace/ftrace/core' into HEAD
config: riscv-randconfig-r042-20220314 (https://download.01.org/0day-ci/archive/20220317/202203172141.n0ep448q-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project a6ec1e3d798f8eab43fb3a91028c6ab04e115fcb)
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/ammarfaizi2/linux-block/commit/87a21b60077d8cb23d3e70a00a969b542d0695d8
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block rostedt/linux-trace/merge-next-20220315
git checkout 87a21b60077d8cb23d3e70a00a969b542d0695d8
# save the config file to linux build tree
mkdir build_dir
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+0x296750): Section mismatch in reference from the variable nft_rt_type to the function .init.text:set_reset_devices()
The variable nft_rt_type 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:
--
>> WARNING: modpost: vmlinux.o(.data+0x296764): Section mismatch in reference from the variable nft_rt_type to the variable .init.text:.Ltmp2
The variable nft_rt_type references
the variable __init .Ltmp2
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+0x34cb00): Section mismatch in reference from the function nfs3_proc_unlink_rpc_prepare() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x34cb4c): Section mismatch in reference from the function nfs3_proc_rename_rpc_prepare() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3500aa): Section mismatch in reference from the function nfs3_xdr_enc_getacl3args() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3ebc5c): Section mismatch in reference from the function ufs_rename() to the variable .init.text:.LBB130_20
<< WARNING: modpost: vmlinux.o(.text+0x3ebc82): Section mismatch in reference from the function ufs_rename() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3ebe14): Section mismatch in reference from the function ufs_error() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3ebf6e): Section mismatch in reference from the function ufs_panic() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3f1722): Section mismatch in reference from the function ufs_nfs_get_inode() to the variable .init.text:.LBB130_23
<< WARNING: modpost: vmlinux.o(.text+0x3f27c4): Section mismatch in reference from the function jffs2_compressors_exit() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x35026e): Section mismatch in reference from the function nfs3_xdr_enc_setacl3args() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x34cb00): Section mismatch in reference from the function nfs3_proc_unlink_rpc_prepare() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x34cb4c): Section mismatch in reference from the function nfs3_proc_rename_rpc_prepare() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3500aa): Section mismatch in reference from the function nfs3_xdr_enc_getacl3args() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3ebc5c): Section mismatch in reference from the function ufs_rename() to the variable .init.text:.LBB130_20
<< WARNING: modpost: vmlinux.o(.text+0x3ebc82): Section mismatch in reference from the function ufs_rename() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3ebe14): Section mismatch in reference from the function ufs_error() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3ebf6e): Section mismatch in reference from the function ufs_panic() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x3f1722): Section mismatch in reference from the function ufs_nfs_get_inode() to the variable .init.text:.LBB130_23
<< WARNING: modpost: vmlinux.o(.text+0x3f27c4): Section mismatch in reference from the function jffs2_compressors_exit() to the function .init.text:set_reset_devices()
<< WARNING: modpost: vmlinux.o(.text+0x35026e): Section mismatch in reference from the function nfs3_xdr_enc_setacl3args() to the function .init.text:set_reset_devices()
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-17 14: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=202203172141.n0ep448q-lkp@intel.com \
--to=lkp@intel.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®