linux-kernel - Re: Re[2]: Where did find

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]

Date:	Tue, 21 Nov 2006 16:16:34 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Paul Sokolovsky <pmiscml@...il.com>
Cc:	Adrian Bunk <bunk@...sta.de>, Greg KH <gregkh@...e.de>,
	Jiri Slaby <jirislaby@...il.com>, linux-kernel@...r.kernel.org,
	kernel-discuss@...dhelds.org
Subject: Re: Re[2]: Where did find_bus() go in 2.6.18?

>   And removing a method from an integral, high-level API set is not the
> same as killing static variable in a hardware driver.

removing dead code that nobody is using should be applauded though. 
If we left all unused code in the kernel binary we'd soon have a 100Mb
vmlinuz file.... and an unmaintainable mess.

Actively removing parts of the kernel code that nobody is using is a
fight against that bloat (and yes the kernel has grown far too big
already, as I'm sure the handheld.org people already know... you
wouldn't want a 2x bigger vmlinuz right?...

Also, if an API or part of an API is unused, it's quite possibly an API
that SHOULDN'T be used, either because it's designed totally shite (like
sleep_on() is :), because the implementation is really horrid or because
it offers a function that nobody actually needs.

All three are grounds for removal to keep the vmlinuz side down in my
book. That isn't change for change's sake (I'm starting to sound like a
Harry Potter book) but that's an attempt to keep the bloat of the
vmlinuz down.

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

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