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:	Mon, 10 Sep 2007 10:08:08 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Adrian Bunk <bunk@...nel.org>, perex@...e.cz,
	linux-kernel@...r.kernel.org
Subject: Re: [-mm patch] unexport sys_{open,read}

On Sun, Sep 09, 2007 at 02:59:40PM -0700, Andrew Morton wrote:
> Sure.  But I think it is better to give people some warning when we're
> planning on breaking out-of-tree things.  I do occasionally receive reports
> of "hey, the X driver which I get from Y doesn't work any more".  Often
> it's open-source stuff, too.  I see no point in irritating our users more than
> we need to.

There is no fucking reason they should have used it in the first place.
Until we have something like a coherent export API instead of random crap
exported because someone once needed it to do a dumb thing it'll happen.
Only way to avoid it is to merge the driver and shake out their dumb ideas
in the review process.

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

And I think almost everyone disagrees with you.  We just carry too much
crap around because of your subborness in this issue, and it gets really
annoying to have some high up on the food chain fighting his longly flight
against the other people.
-
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/