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] [day] [month] [year] [list]
Date:	Tue, 25 Sep 2007 08:13:28 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: lib-y vs EXPORT_SYMBOL: who wins?

On Tue, Sep 25, 2007 at 03:07:44PM +1000, Rusty Russell wrote:
> Various files under lib/ are linked into a .a so they only get linked if
> needed.  But many of these functions are also EXPORT_SYMBOL()ed.
> 
> This doesn't really make sense: if it's exported it really needs to be
> present.  Certain configurations can hit this (lguest uses kasprintf,
> and can be a module).
> 
> We could do something hacky and try to figure out if any modules need
> the symbols, which screws modules built later, but is no worse than a
> CONFIG_-based solution.
> 
> Or to we just move all the exported functions out of the .a?


I am all for killing lib-y altogether. But do not want to sacrify
kernel bloat for this.
hch suggested a bit of Kconfig tricekery and that seems
like an OK plan to me.
But I'm not in a position to do the detective work at the moment -
feed up with oter stuff for now.

	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

Powered by Openwall GNU/*/Linux Powered by OpenVZ