From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: oe-kbuild-all@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Subject: [stable:linux-5.15.y 6778/9999] WARNING: modpost: vmlinux.o(.text.unlikely+0x3c08): Section mismatch in reference from the function io_uring_drop_tctx_refs() to the variable .init.data:initcall_level_names
Date: Sat, 22 Apr 2023 16:34:21 +0800 [thread overview]
Message-ID: <202304221603.LooNetGu-lkp@intel.com> (raw)
Hi Jens,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.15.y
head: 3299fb36854fdc288bddc2c4d265f8a2e5105944
commit: f435c66d2336fff104e2c3cbfff60905733e7d89 [6778/9999] io_uring: move to separate directory
config: xtensa-randconfig-r002-20230421 (https://download.01.org/0day-ci/archive/20230422/202304221603.LooNetGu-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 12.1.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/stable/linux-stable.git/commit/?id=f435c66d2336fff104e2c3cbfff60905733e7d89
git remote add stable https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
git fetch --no-tags stable linux-5.15.y
git checkout f435c66d2336fff104e2c3cbfff60905733e7d89
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=xtensa olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=xtensa SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304221603.LooNetGu-lkp@intel.com/
All warnings (new ones prefixed by >>, old ones prefixed by <<):
<< WARNING: modpost: vmlinux.o(.text.unlikely+0x3c08): Section mismatch in reference from the function test_ahash_jiffies.isra.0() to the variable .init.data:initcall_level_names
>> WARNING: modpost: vmlinux.o(.text.unlikely+0x3c08): Section mismatch in reference from the function io_uring_drop_tctx_refs() to the variable .init.data:initcall_level_names
The function io_uring_drop_tctx_refs() references
the variable __initdata initcall_level_names.
This is often because io_uring_drop_tctx_refs lacks a __initdata
annotation or the annotation of initcall_level_names is wrong.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-22 8:34 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=202304221603.LooNetGu-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sashal@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 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.