From: Fengguang Wu <fengguang.wu@intel.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Dmitry Kasatkin <dmitry.kasatkin@intel.com>,
Chris Zankel <chris@zankel.net>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: 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
Date: Sat, 10 Nov 2012 10:26:59 +0800 [thread overview]
Message-ID: <20121110022659.GC6486@localhost> (raw)
In-Reply-To: <509d3c29.gB8n+wTWMkx5wadt%fengguang.wu@intel.com>
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
parent reply other threads:[~2012-11-10 2:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <509d3c29.gB8n+wTWMkx5wadt%fengguang.wu@intel.com>]
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=20121110022659.GC6486@localhost \
--to=fengguang.wu@intel.com \
--cc=chris@zankel.net \
--cc=dmitry.kasatkin@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.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