From: kernel test robot <lkp@intel.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: oe-kbuild-all@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>
Subject: [stable:linux-5.10.y 119/9999] WARNING: modpost: lib/test_bitmap.o(.text.unlikely+0xd8): Section mismatch in reference from the function bitmap_equal() to the variable .init.rodata:clump_exp
Date: Tue, 25 Jul 2023 01:44:00 +0800 [thread overview]
Message-ID: <202307250102.tkAnbAPJ-lkp@intel.com> (raw)
Hi Paul,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.10.y
head: 381518b4a9165cd793599c1668c82079fcbcbe1f
commit: b506450ce3d904386c1bd7e33c74f9343548d2d8 [119/9999] seccomp: Add missing return in non-void function
config: xtensa-randconfig-r032-20230724 (https://download.01.org/0day-ci/archive/20230725/202307250102.tkAnbAPJ-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230725/202307250102.tkAnbAPJ-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202307250102.tkAnbAPJ-lkp@intel.com/
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: lib/test_bitmap.o(.text.unlikely+0xd8): Section mismatch in reference from the function bitmap_equal() to the variable .init.rodata:clump_exp
The function bitmap_equal() references
the variable __initconst clump_exp.
This is often because bitmap_equal lacks a __initconst
annotation or the annotation of clump_exp is wrong.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-24 17:44 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=202307250102.tkAnbAPJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@crapouillou.net \
/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.