linux-kernel - Re: ARM: Section mismatch warnings

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: <20070528192548.GD5737@flint.arm.linux.org.uk>
Date:	Mon, 28 May 2007 20:25:48 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	linux-arm-kernel@...ts.arm.linux.org.uk,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: ARM: Section mismatch warnings

On Mon, May 28, 2007 at 08:36:29PM +0200, Sam Ravnborg wrote:
> > 
> > > o-arm-neponset/log.out:WARNING: arch/arm/mach-sa1100/built-in.o(.text+0x1748):
> >  Section mismatch: reference to .init.text:sa1110_mb_disable
> >  (between 'neponset_init' and 'neponset_resume')
> > 
> > This one looks quite bogus.  sa1110_mb_disable() is marked __init, and
> > it's called from neponset_init() which is also marked __init.
> 
> Created a neponset.i file - output:
> 
> static int neponset_init(void)
> {
>  platform_driver_register(&neponset_device_driver);
> 
> So we loose the __init marker during preprocessing.
> Which is due the the buggy part of my path that adds __devinit.
> 
> There was a reason I noted the devinit markers should be reviewed
> carefully - this one seems wrong.

I don't understand why you added that __devinit in the first place.
What happens if you leave it as a mere __init function, as it should be?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
-
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/