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: <469F749F.8030606@s5r6.in-berlin.de>
Date:	Thu, 19 Jul 2007 16:26:39 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Arjan van de Ven <arjan@...ux.intel.com>
Subject: Re: does CONFIG_UNUSED_SYMBOLS have any value anymore?

Robert P. J. Day wrote:
...
> it's not clear if that means that it was a *one-time* transition
> aid which is now unnecessary, or whether it's an *ongoing* aid which
> might be used at any time.  currently, there are no invocations of
> EXPORT_UNUSED_SYMBOL[_GPL] anywhere in the tree.  so does that mean
> this feature can be tossed?  or might it still be used every so often?

git-blame (or qgit, which I actually used) points from this part of
lib/Kconfig.debug to the following chunk in
Documentation/feature-removal-schedule.txt:

What:	Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
	(temporary transition config option provided until then)
	The transition config option will also be removed at the same time.
When:	before 2.6.19
Why:	Unused symbols are both increasing the size of the kernel binary
	and are often a sign of "wrong API"
Who:	Arjan van de Ven <arjan@...ux.intel.com>
-- 
Stefan Richter
-=====-=-=== -=== =--==
http://arcgraph.de/sr/
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ