linux-kernel - lib-y vs EXPORT

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-next>] [day] [month] [year] [list]

Message-Id: <1190696865.27805.317.camel@localhost.localdomain>
Date:	Tue, 25 Sep 2007 15:07:44 +1000
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: lib-y vs EXPORT_SYMBOL: who wins?

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 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/