From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Yujie Liu <yujie.liu@intel.com>
Cc: kernel test robot <lkp@intel.com>,
jcmvbkbc@gcc.gnu.org, oe-kbuild-all@lists.linux.dev,
netdev@vger.kernel.org, Herve Codina <herve.codina@bootlin.com>
Subject: Re: [net-next:main 4/19] WARNING: modpost: vmlinux: section mismatch in reference: bitmap_copy_clear_tail+0x58 (section: .text.unlikely) -> __setup_str_initcall_blacklist (section: .init.rodata)
Date: Thu, 14 Mar 2024 15:15:22 +0200 [thread overview]
Message-ID: <ZfL4amLH5W9Zc_MS@smile.fi.intel.com> (raw)
In-Reply-To: <ZfLGLmb3QAsIGlbB@yujie-X299>
On Thu, Mar 14, 2024 at 05:41:02PM +0800, Yujie Liu wrote:
> Hi Andy,
>
> On Wed, Mar 13, 2024 at 09:22:13PM +0200, Andy Shevchenko wrote:
> > On Tue, Mar 12, 2024 at 10:29:16AM +0800, kernel test robot wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git main
> > > head: f095fefacdd35b4ea97dc6d88d054f2749a73d07
> > > commit: de5f84338970815b9fdd3497a975fb572d11e0b5 [4/19] lib/bitmap: Introduce bitmap_scatter() and bitmap_gather() helpers
> > > config: xtensa-randconfig-001-20240311 (https://download.01.org/0day-ci/archive/20240312/202403121032.WDY8ftKq-lkp@intel.com/config)
> > > compiler: xtensa-linux-gcc (GCC) 13.2.0
> > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240312/202403121032.WDY8ftKq-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/202403121032.WDY8ftKq-lkp@intel.com/
> > >
> > > All warnings (new ones prefixed by >>, old ones prefixed by <<):
> > >
> > > WARNING: modpost: missing MODULE_DESCRIPTION() in vmlinux.o
> > > WARNING: modpost: vmlinux: section mismatch in reference: put_page+0x58 (section: .text.unlikely) -> initcall_level_names (section: .init.data)
> > > >> WARNING: modpost: vmlinux: section mismatch in reference: bitmap_copy_clear_tail+0x58 (section: .text.unlikely) -> __setup_str_initcall_blacklist (section: .init.rodata)
> >
> > Reminds me of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938
>
> Thanks for the information. We will configure the bot to ignore this
> pattern thus to avoid false reports.
I haven't told they are false.
I Cc'ed Max who can shed a light on this.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-03-14 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 2:29 [net-next:main 4/19] WARNING: modpost: vmlinux: section mismatch in reference: bitmap_copy_clear_tail+0x58 (section: .text.unlikely) -> __setup_str_initcall_blacklist (section: .init.rodata) kernel test robot
2024-03-13 19:22 ` Andy Shevchenko
2024-03-14 9:41 ` Yujie Liu
2024-03-14 13:15 ` Andy Shevchenko [this message]
2024-03-15 1:33 ` Yujie Liu
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=ZfL4amLH5W9Zc_MS@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=herve.codina@bootlin.com \
--cc=jcmvbkbc@gcc.gnu.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yujie.liu@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).