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)

[Yujie Liu <yujie.liu@intel.com>]

On Thu, Mar 14, 2024 at 03:15:22PM +0200, Andy Shevchenko wrote:
> 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.

Oh, sorry for the misunderstanding. We will let the bot keep capturing
this issue and stay tuned for comments from Max and GCC folks.

Best Regards,
Yujie