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] [day] [month] [year] [list]

Date:	Tue, 25 Sep 2007 17:17:44 -0400
From:	Dave Jones <davej@...hat.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	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, Sep 10, 2007 at 04:14:56PM +0100, Arjan van de Ven wrote:

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

We've both done the same job, so it's unsurprising that we share the
same view on this.  A number of times I've had out of tree module
authors complaining to _me_ because "Fedora fucked up my module, it
works fine in $otherdistro"  (ignoring the fact that $otherdistro
is a point release or more behind Fedora).

There's definitly a culture-gap between some out-of-tree module
authors and people who intend from day 1 to get their code merged
into mainline.  The former don't know what happens in mainline
until several distros start moving onto newer kernels, so no amount
of warnings is going to help these people.

	Dave

-- 
http://www.codemonkey.org.uk
-
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/