linux-kernel - 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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <509AEF68.5060004@zankel.net>
Date:	Wed, 07 Nov 2012 15:31:52 -0800
From:	Chris Zankel <chris@...kel.net>
To:	Fengguang Wu <fengguang.wu@...el.com>
CC:	"Kasatkin, Dmitry" <dmitry.kasatkin@...el.com>,
	Sam Ravnborg <sam@...nborg.org>,
	Mimi Zohar <zohar@...ux.vnet.ibm.com>,
	linux-security-module@...r.kernel.org,
	linux-kbuild <linux-kbuild@...r.kernel.org>,
	LKML <linux-kernel@...r.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

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@...el.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@...el.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@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/