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  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]
Date:	Mon, 4 Feb 2008 06:13:18 +0100
From:	Sam Ravnborg <>
To:	Peter Teoh <>
Cc:	LKML <>
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

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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists