Re: lib-y vs EXPORT_SYMBOL: who wins?

Previous thread: Re: [RFC] New kernel-message logging API by linux on Tuesday, September 25, 2007 - 12:58 am. (4 messages)

Next thread: [git patches] net driver fixes by Jeff Garzik on Tuesday, September 25, 2007 - 1:08 am. (1 message)
To: lkml - Kernel Mailing List <linux-kernel@...>
Cc: Sam Ravnborg <sam@...>, Andrew Morton <akpm@...>
Date: Tuesday, September 25, 2007 - 1:07 am

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?

Cheers,
Rusty.

-

To: Rusty Russell <rusty@...>
Cc: lkml - Kernel Mailing List <linux-kernel@...>, Andrew Morton <akpm@...>
Date: Tuesday, September 25, 2007 - 2:13 am

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
-

Previous thread: Re: [RFC] New kernel-message logging API by linux on Tuesday, September 25, 2007 - 12:58 am. (4 messages)

Next thread: [git patches] net driver fixes by Jeff Garzik on Tuesday, September 25, 2007 - 1:08 am. (1 message)