linux-kernel - Re: Bogus section mismatch errors?

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] [day] [month] [year] [list]

Date:	Wed, 9 May 2007 18:59:54 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: Bogus section mismatch errors?

On Tue, May 08, 2007 at 01:52:20PM +0200, Sam Ravnborg wrote:
> On Tue, May 08, 2007 at 12:17:59PM +0100, Russell King wrote:
> > WARNING: mm/built-in.o - Section mismatch:
> >  reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x1bd94)
> >  and 'cache_reap'
> > WARNING: mm/built-in.o - Section mismatch:
> >  reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x1bdcc)
> >  and 'cache_reap'
> There are in slab a function that is not marked __init that refer to a function marked
> __init. But the logic surrounding makes it OK.
> 
> I have no fix/workaround for this.
> Andres has suggested that we should mark functions/data that may refer to __init{data}
> with something like: __nowarn and __nowarndata
> 
Here's one I've started getting with the quicklist changes:

WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x1ba5c) and 'quicklist_total_size'

quicklist_total_size() is not marked __init, nor is show_mem() in
arch/sh/mm/init.c, where I've added the reference. Ideas?
-
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/