linux-kernel - Re: Coexistence of EXPORT_SYMBOL() and _

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20080205154818.cdf2dbaf.randy.dunlap@oracle.com>
Date:	Tue, 5 Feb 2008 15:48:18 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Peter Teoh <htmldeveloper@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Coexistence of EXPORT_SYMBOL() and __cpuinit

On Mon, 4 Feb 2008 06:13:18 +0100 Sam Ravnborg wrote:

> On Mon, Feb 04, 2008 at 09:49:24AM +0800, Peter Teoh wrote:
> > In kernel/cpu.c, there exists API that is declared as __cpuinit, and
> > at the same time exported via EXPORT_SYMBOL().
> > 
> > Can these two attribute coexists at the same time?   I mean, when it
> > is declared with EXPORT_SYMBOL, according to include/linux/module.h,
> > it is placed in a __ksymtab section, and when compiled with with
> > __cpuinit, according to include/linux/init.h, into a __cpuinit
> > section.
> 
> kbuild.git contains a commit so we no longer warn about
> symbols being exported if annotatated with __cpuinit, __devinit, and
> __devinit.

but why?  Is this just to reduce the volume of output, even though
exported __init symbols are a problem waiting to happen?


> I've requested Linus to pull the changes and expet it to happen
> within the next two days.


---
~Randy
--
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/