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
| ||
|
Date: Mon, 4 Feb 2008 06:13:18 +0100 From: Sam Ravnborg <sam@...nborg.org> To: Peter Teoh <htmldeveloper@...il.com> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: Coexistence of EXPORT_SYMBOL() and __cpuinit 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. I've requested Linus to pull the changes and expet it to happen within the next two days. Sam -- 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/
Powered by blists - more mailing lists