From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [kees:flexcpy/next-20220502 31/34] WARNING: modpost: vmlinux.o(.text+0xe79f2a): Section mismatch in reference from the function ieee80211_find_sta() to the variable .init.text:.L0
Date: Thu, 5 May 2022 07:19:30 +0800 [thread overview]
Message-ID: <202205050704.5LotcLcz-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git flexcpy/next-20220502
head: 1dbd8181297512b190aca23477043ac635daba4e
commit: b0fdcfe7030e00d582776443aabf76d8653104dc [31/34] xtensa: Use mem_to_flex_dup() with struct property
config: riscv-randconfig-r023-20220501 (https://download.01.org/0day-ci/archive/20220505/202205050704.5LotcLcz-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 11.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/kees/linux.git/commit/?id=b0fdcfe7030e00d582776443aabf76d8653104dc
git remote add kees https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
git fetch --no-tags kees flexcpy/next-20220502
git checkout b0fdcfe7030e00d582776443aabf76d8653104dc
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 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(.text+0xe79f2a): Section mismatch in reference from the function ieee80211_find_sta() to the variable .init.text:.L0
The function ieee80211_find_sta() references
the variable __init .L0 .
This is often because ieee80211_find_sta lacks a __init
annotation or the annotation of .L0 is wrong.
Note: the below error/warnings can be found in parent commit:
<< WARNING: modpost: vmlinux.o(.text+0xc57482): Section mismatch in reference from the function snd_soc_jack_report() to the function .init.text:oom_init()
<< WARNING: modpost: vmlinux.o(.text+0xc574aa): Section mismatch in reference from the function snd_soc_jack_add_zones() to the variable .init.text:$x
<< WARNING: modpost: vmlinux.o(.text+0xe56854): Section mismatch in reference from the function cfg80211_report_obss_beacon_khz() to the function .init.text:mt7621_pci_phy_driver_init()
<< WARNING: modpost: vmlinux.o(__ex_table+0x11a0): Section mismatch in reference from the variable .L0 to the variable .debug_str:.LASF2051
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-04 23:48 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=202205050704.5LotcLcz-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.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