Re: WARNING: vmlinux.o(.text.unlikely+0x3e94): Section mismatch in reference from the function bitmap_copy_clear_tail() to the variable .init.rodata:__setup_str_initcall_blacklist

[Andy Shevchenko <andy.shevchenko@gmail.com>]

On Sat, Feb 8, 2020 at 2:03 AM kbuild test robot <lkp@intel.com> wrote:
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   90568ecf561540fa330511e21fcd823b0c3829c6
> commit: 30544ed5de431fe25d3793e4dd5a058d877c4d77 lib/bitmap: introduce bitmap_replace() helper
> date:   9 weeks ago
> config: xtensa-randconfig-a001-20200208 (attached as .config)
> compiler: xtensa-linux-gcc (GCC) 7.5.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout 30544ed5de431fe25d3793e4dd5a058d877c4d77
>         # save the attached .config to linux build tree
>         GCC_VERSION=7.5.0 make.cross ARCH=xtensa
>

The discussion is happening here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938

> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> >> WARNING: vmlinux.o(.text.unlikely+0x3e94): Section mismatch in reference from the function bitmap_copy_clear_tail() to the variable .init.rodata:__setup_str_initcall_blacklist
>    The function bitmap_copy_clear_tail() references
>    the variable __initconst __setup_str_initcall_blacklist.
>    This is often because bitmap_copy_clear_tail lacks a __initconst
>    annotation or the annotation of __setup_str_initcall_blacklist is wrong.
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org



-- 
With Best Regards,
Andy Shevchenko