linux-kernel - Re: [PATCH] Move kasprintf.o to obj-y

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: <20070924080948.GA8525@infradead.org>
Date:	Mon, 24 Sep 2007 09:09:48 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Alexey Dobriyan <adobriyan@...ru>, akpm@...l.org,
	linux-kernel@...r.kernel.org, devel@...nvz.org
Subject: Re: [PATCH] Move kasprintf.o to obj-y

On Mon, Sep 24, 2007 at 09:59:49AM +0200, Sam Ravnborg wrote:
> > Please kill lib-y while you're at it.  It's useless and a constant
> > source of pain like this.
> Kernel-bloat is another "constant source of pain".
> But the troubles are that increased blot does not result in compiler erros.
> 
> And your proposal to kil lib-y is a counter-act here.

Killing lib-y doesn't create kernel bloat if done right.  Just introduce
proper Kconfig dependencies for the truely optional parts.  But if you
look at the list of objects in lib-y you'll see that they fall in basically
three categories:

 (1) always used by core code - should be obj-y
 (2) generic implementation for arch-specific functionality, should be
     guarded by Kconfig for clarity reasons anyway
 (3) library code often but not always used by code that's not always
     built in.  Here we run into the move to obj-y to avoid compiler
     warning when used as module issue all the time.  Adding a CONFIG
     for the bigger onces actually avoids bloat over obj-y here, and
     when it's small enough obj-y is a lot safer in the presence of
     modular users

Really, trying to use the old static library use on demand concept simply
doesn't fit the way the kernel is built with it's modules and dependencies.
-
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/