[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ba6caea-654e-4dcd-a4a4-bfdcf808f0e5@intel.com>
Date: Thu, 22 Aug 2024 10:23:04 +0200
From: Przemek Kitszel <przemyslaw.kitszel@...el.com>
To: kernel test robot <lkp@...el.com>, <oe-kbuild-all@...ts.linux.dev>, "Max
Filippov" <jcmvbkbc@...il.com>
CC: <linux-kernel@...r.kernel.org>, Pawel Chmielewski
<pawel.chmielewski@...el.com>, Jacob Keller <jacob.e.keller@...el.com>, "Paul
Greenwalt" <paul.greenwalt@...el.com>, Simon Horman <horms@...nel.org>, "Tony
Nguyen" <anthony.l.nguyen@...el.com>
Subject: Re: WARNING: [xtensa] modpost: vmlinux: section mismatch in
reference: ice_adv_lnk_speed_maps+0x14 (section: .data) ->
__setup_str_initcall_blacklist (section: .init.rodata)
On 8/22/24 01:24, kernel test robot wrote:
> Hi Pawel,
>
> FYI, the error/warning still remains.
Apologies that we did not replied to the original report.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: b311c1b497e51a628aa89e7cb954481e5f9dced2
> commit: 982b0192db455d288fc1deb06632f529c35daa15 ice: Refactor finding advertised link speed
> date: 10 months ago
> config: xtensa-randconfig-r123-20240821 (https://download.01.org/0day-ci/archive/20240822/202408220755.LlaA10C6-lkp@intel.com/config)
I wonder why there is 6.6 kernel used, perhaps not a big deal.
> compiler: xtensa-linux-gcc (GCC) 14.1.0
> reproduce: (https://download.01.org/0day-ci/archive/20240822/202408220755.LlaA10C6-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@...el.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202408220755.LlaA10C6-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+0x78 (section: .text.unlikely) -> initcall_level_names (section: .init.data)
>>> WARNING: modpost: vmlinux: section mismatch in reference: ice_adv_lnk_speed_maps+0x14 (section: .data) -> __setup_str_initcall_blacklist (section: .init.rodata)
I have spent just half of hour on that and I'm clueless.
For reference, the driver code is:
static const u32 arr_name[] __initconst = {
SOME_CONST,
};
and core kernel has:
#define __initconst __section(.init.rodata)
@Max Filippov, you have authored much of xtensa arch for kernel,
especially XIP support, and touched .init.rodata back then;
perhaps you have any idea what is going here?
> WARNING: modpost: vmlinux: section mismatch in reference: ice_adv_lnk_speed_maps+0x30 (section: .data) -> __setup_str_initcall_blacklist (section: .init.rodata)
> WARNING: modpost: vmlinux: section mismatch in reference: ice_adv_lnk_speed_maps+0x4c (section: .data) -> __setup_str_initcall_blacklist (section: .init.rodata)
> WARNING: modpost: vmlinux: section mismatch in reference: ice_adv_lnk_speed_maps+0x68 (section: .data) -> __setup_str_initcall_blacklist (section: .init.rodata)
> WARNING: modpost: vmlinux: section mismatch in reference: ice_adv_lnk_speed_maps+0x84 (section: .data) -> __setup_str_initcall_blacklist (section: .init.rodata)
> WARNING: modpost: vmlinux: section mismatch in reference: ice_adv_lnk_speed_maps+0xa0 (section: .data) -> __setup_str_initcall_blacklist (section: .init.rodata)
> WARNING: modpost: vmlinux: section mismatch in reference: ice_adv_lnk_speed_maps+0xbc (section: .data) -> __setup_str_initcall_blacklist (section: .init.rodata)
> WARNING: modpost: vmlinux: section mismatch in reference: ice_adv_lnk_speed_maps+0xd8 (section: .data) -> __setup_str_initcall_blacklist (section: .init.rodata)
> WARNING: modpost: vmlinux: section mismatch in reference: ice_adv_lnk_speed_maps+0xf4 (section: .data) -> __setup_str_initcall_blacklist (section: .init.rodata)
>
Powered by blists - more mailing lists