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]

Message-ID: <20070910161456.7431312c@laptopd505.fenrus.org>
Date:	Mon, 10 Sep 2007 16:14:56 +0100
From:	Arjan van de Ven <arjan@...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 Mon, 10 Sep 2007 02:23:24 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:

> I would like to see "everyone" explain what we lose by giving
> developers a bit of warning before we break their stuff.

here's the skinny: 99% of the external module developers won't notice
until they're gone, even with the warning. And that's an optimistic
estimate. Warnings don't work for this.

All this kind of thing buys us is an excuse so that we can say "but we
warned  you for 3 months". It doesn't actually change anything else.

Maybe I'm too pessimistic in my assumption that external open module
writers don't actually follow mainline closely; and maybe part of me
would love for them to follow it closer, so close that they would even
consider submitting their driver for it. But sadly from experience...
warnings dont' work. Only when things break hard people notice.
-
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/