* Re: [digsig:dmi 20/39] WARNING: security/built-in.o(.text+0xb43ac): Section mismatch in reference from the function integrity_init_keyring() to the variable .init.data:chosen_lsm
[not found] <509d3c29.gB8n+wTWMkx5wadt%fengguang.wu@intel.com>
@ 2012-11-10 2:26 ` Fengguang Wu
0 siblings, 0 replies; only message in thread
From: Fengguang Wu @ 2012-11-10 2:26 UTC (permalink / raw)
To: Mimi Zohar; +Cc: Dmitry Kasatkin, Chris Zankel, linux-kbuild
Hi Mimi, Dmitry,
Sorry please ignore this and the following Section mismatch warnings,
they are likely false ones:
On 11/07/2012 03:31 PM, Chris Zankel wrote:
>
> Looking a bit into it, I think modpost is broken. I'm working on a fix.
This is specific to Xtensa. Symbols are stored in a separate '.lit'
section, but modpost doesn't seem to currently resolve it correctly.
Chris: it also happens to ARCH=sh builds.
Thanks,
Fengguang
On Sat, Nov 10, 2012 at 01:23:53AM +0800, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/kasatkin/linux-digsig.git dmi
> head: 62d02cdf591eea161bc78c2430ba08b6d138eae5
> commit: 3868ad2d648d8abd7a645d101ff53e5b369c632b [20/39] integrity: create and inititialize a keyring with builtin public key
> config: make ARCH=sh allyesconfig
>
> All warnings:
>
> WARNING: security/built-in.o(.text+0xb43ac): Section mismatch in reference from the function integrity_init_keyring() to the variable .init.data:chosen_lsm
> The function integrity_init_keyring() references
> the variable __initdata chosen_lsm.
> This is often because integrity_init_keyring lacks a __initdata
> annotation or the annotation of chosen_lsm is wrong.
>
> ---
> 0-DAY kernel build testing backend Open Source Technology Center
> Fengguang Wu, Yuanhan Liu Intel Corporation
^ permalink raw reply [flat|nested] only message in thread