From: Fengguang Wu <fengguang.wu@intel.com>
To: "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-security-module@vger.kernel.org,
linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [digsig:dmi 20/35] WARNING: security/integrity/built-in.o(.text+0x1d8): Section mismatch in reference from the function integrity_inode_free() to the variable .init.data:ima_use_tcb
Date: Tue, 6 Nov 2012 19:57:16 +0800 [thread overview]
Message-ID: <20121106115716.GA21889@localhost> (raw)
In-Reply-To: <CALLzPKb-9uHdbqUujbcQ2z38Lv5sqBKtmYmjYDdVhgVs4WF6cg@mail.gmail.com>
Perhaps we should CC more people..
On Tue, Nov 06, 2012 at 01:47:18PM +0200, Kasatkin, Dmitry wrote:
> On Tue, Nov 6, 2012 at 1:41 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > On Tue, Nov 06, 2012 at 01:16:16PM +0200, Kasatkin, Dmitry wrote:
> >> Hi,
> >>
> >> I do not see that integrity_inode_free() uses ima_use_tcb.
> >>
> >> I think it is false positive.
> >
> > Interestingly, when trying to reproduce the problem, I got this
> > slightly different message:
Now after make clean, I get both the warnings on ima_use_tcb and
chosen_lsm.
> > WARNING: security/built-in.o(.text+0x2b68c): Section mismatch in reference from the function integrity_inode_free() to the variable .init.d
> > ata:chosen_lsm
> > The function integrity_inode_free() references
> > the variable __initdata chosen_lsm.
> > This is often because integrity_inode_free lacks a __initdata
> > annotation or the annotation of chosen_lsm is wrong.
> >
>
> Hello,
>
> chosen_lsm has nothing to do with integrity subsystem, though
> integrity_inode_free() is called from security_inode_free(),
> which is part of security subsystem files which uses chosen_lsm...
>
> That is very strange.
>
> - Dmitry
>
>
> > Thanks,
> > Fengguang
> >
> >> On Wed, Oct 31, 2012 at 5:11 PM, kbuild test robot
> >> <fengguang.wu@intel.com> wrote:
> >> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/kasatkin/linux-digsig.git dmi
> >> > head: 2309bb884f94d84ecb1a6a176d3e8199de7d6dad
> >> > commit: 13ba29dcf6f0021a14a04f6f3a4560a399c02b34 [20/35] integrity: create and inititialize a keyring with builtin public key
> >> > config: make ARCH=xtensa allyesconfig
> >> >
> >> > All warnings:
> >> >
> >> > WARNING: security/integrity/built-in.o(.text+0x1d8): Section mismatch in reference from the function integrity_inode_free() to the variable .init.data:ima_use_tcb
> >> > The function integrity_inode_free() references
> >> > the variable __initdata ima_use_tcb.
> >> > This is often because integrity_inode_free lacks a __initdata
> >> > annotation or the annotation of ima_use_tcb is wrong.
> >> >
> >> > ---
> >> > 0-DAY kernel build testing backend Open Source Technology Center
> >> > Fengguang Wu, Yuanhan Liu Intel Corporation
next parent reply other threads:[~2012-11-06 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50913fa5.uJnC6BQdkN/Xw1h0%fengguang.wu@intel.com>
[not found] ` <CALLzPKZdh9a0nT52GOZEO7dgxtLqU_VwD27Qs_gBe-bSk=J87g@mail.gmail.com>
[not found] ` <20121106114108.GB19965@localhost>
[not found] ` <CALLzPKb-9uHdbqUujbcQ2z38Lv5sqBKtmYmjYDdVhgVs4WF6cg@mail.gmail.com>
2012-11-06 11:57 ` Fengguang Wu [this message]
2012-11-07 23:31 ` [digsig:dmi 20/35] WARNING: security/integrity/built-in.o(.text+0x1d8): Section mismatch in reference from the function integrity_inode_free() to the variable .init.data:ima_use_tcb Chris Zankel
2012-11-07 23:36 ` Chris Zankel
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=20121106115716.GA21889@localhost \
--to=fengguang.wu@intel.com \
--cc=dmitry.kasatkin@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).