* 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
[not found] ` <CALLzPKb-9uHdbqUujbcQ2z38Lv5sqBKtmYmjYDdVhgVs4WF6cg@mail.gmail.com>
@ 2012-11-06 11:57 ` Fengguang Wu
2012-11-07 23:31 ` Chris Zankel
0 siblings, 1 reply; 3+ messages in thread
From: Fengguang Wu @ 2012-11-06 11:57 UTC (permalink / raw)
To: Kasatkin, Dmitry
Cc: Sam Ravnborg, Mimi Zohar, linux-security-module, linux-kbuild,
LKML
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* 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
2012-11-06 11:57 ` [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 Fengguang Wu
@ 2012-11-07 23:31 ` Chris Zankel
2012-11-07 23:36 ` Chris Zankel
0 siblings, 1 reply; 3+ messages in thread
From: Chris Zankel @ 2012-11-07 23:31 UTC (permalink / raw)
To: Fengguang Wu
Cc: Kasatkin, Dmitry, Sam Ravnborg, Mimi Zohar, linux-security-module,
linux-kbuild, LKML
Hi,
Looking a bit into it, I think modpost is broken. I'm working on a fix.
Cheers!
-Chris
On 11/06/2012 03:57 AM, Fengguang Wu wrote:
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 3+ messages in thread
* 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
2012-11-07 23:31 ` Chris Zankel
@ 2012-11-07 23:36 ` Chris Zankel
0 siblings, 0 replies; 3+ messages in thread
From: Chris Zankel @ 2012-11-07 23:36 UTC (permalink / raw)
To: Fengguang Wu
Cc: Kasatkin, Dmitry, Sam Ravnborg, Mimi Zohar, linux-security-module,
linux-kbuild, LKML
Pressed the 'send' button a bit too fast.
On 11/07/2012 03:31 PM, Chris Zankel wrote:
> Hi,
>
> 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.
Cheers!
-Chris
>
> Cheers!
> -Chris
>
> On 11/06/2012 03:57 AM, Fengguang Wu wrote:
>> 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
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-11-07 23:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 ` [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 Fengguang Wu
2012-11-07 23:31 ` Chris Zankel
2012-11-07 23:36 ` Chris Zankel
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).