linux-kernel - Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.

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: <20071127212558.GA27481@redhat.com>
Date:	Tue, 27 Nov 2007 16:25:58 -0500
From:	Dave Jones <davej@...hat.com>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Roland Dreier <rdreier@...co.com>, Andi Kleen <ak@...e.de>,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	sam@...nborg.org
Subject: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.

On Tue, Nov 27, 2007 at 10:09:42PM +0100, Adrian Bunk wrote:
 > On Tue, Nov 27, 2007 at 02:00:37PM -0500, Dave Jones wrote:
 > > On Mon, Nov 26, 2007 at 10:25:33AM -0800, Stephen Hemminger wrote:
 > >  
 > >  > 1) Why is everyone so concerned that export symbol space is large?
 > >  > 	- does it cost cpu or running memory?
 > >  > 	- does it cause bugs?
 > >  > 	- or are you just worried about "evil modules"?
 > > 
 > > To clarify something here, by "evil", don't necessarily think "binary only". 
 > > 
 > > Out of tree modules are frequently using symbols that they shouldn't be.
 > > Because they get no peer-review here, they 'get away with it' for the most part.
 > > Until distro vendors push rebased kernel updates that removed exports that
 > > should never have been exported, and suddenly people like me get bombed
 > > with "Fedora broke my xyz driver" mails.
 > >...
 > 
 > The real problem is that these drivers are not in the upstream kernel.

You're preaching to the choir.

 > Are there common reasons why these drivers are not upstream?

It varies case by case.

	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/