linux-kernel - Re: [-mm patch] unexport sys

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:	Sun, 9 Sep 2007 23:41:18 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Christoph Hellwig <hch@...radead.org>, perex@...e.cz,
	linux-kernel@...r.kernel.org
Subject: Re: [-mm patch] unexport sys_{open,read}

On Mon, 10 Sep 2007 00:22:03 +0200
Adrian Bunk <bunk@...nel.org> wrote:

> On Sun, Sep 09, 2007 at 02:59:40PM -0700, Andrew Morton wrote:
> > On Sun, 9 Sep 2007 21:39:20 +0100 Christoph Hellwig
> > <hch@...radead.org> wrote:

> > Adrian knows this, yet he habitually sends zero-warning
> > export-removal patches and I habitually ignore them.  I guess we
> > must both enjoy this or something.
> 
> You might rename EXPORT_UNUSED_SYMBOL to EXPORT_UNUSED_SYMBOL_ADRIAN 
> because AFAIK I am still the only person who was ever dumb enough to
> use it after you wanted me to do so...
> 
> Everyone else is allowed to always add, remove and change exports
> as he likes, but I should go through this special process.
> 
> It makes no sense (except for keeping me busy) to treat some patches
> I send special while changes made by other people that break the
> modules API are still allowed.
> 
> Andrew, please define API rules, IOW rules for addition, removal and 
> changing of exported code, that are valid for *everyone* or go to
> hell with your EXPORT_UNUSED_SYMBOL.

Adrian,

as much as I personally disagree with Andrew's policy here (esp for
these symbols, they have been deprecated for years now), it's trivial
to just follow his requirements and get this over with.

As for who cares.. I do care still, unused exports make the kernel
bigger for everyone, and for the most cases, encourage incorrect APIs
to be used by driver writers (they act as a trap; the symbols generally
are not used by anything in the kernel because they're the wrong API to
use for drivers; having them exported wrongly suggests to new driver
writers that they are good things to use). I plan to do another run of
finding all unused exports and just marking the lot as _UNUSED  exports.
(that's not the same as removing them quite yet, but at least it's a
good warning for driver writers that they should think twice about the
API to see if it's the right one to use)

Greetings,
    Arjan van de Ven
-
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/