linux-kernel - RE: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19]

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:	Thu, 14 Dec 2006 11:49:48 -0800
From:	"Hua Zhong" <hzhong@...il.com>
To:	"'Scott Preece'" <sepreece@...il.com>,
	"'Chris Wedgwood'" <cw@...f.org>
Cc:	"'Eric Sandeen'" <sandeen@...deen.net>,
	"'Christoph Hellwig'" <hch@...radead.org>,
	"'Linus Torvalds'" <torvalds@...l.org>,
	"'Jeff Garzik'" <jeff@...zik.org>, "'Greg KH'" <gregkh@...e.de>,
	"'Jonathan Corbet'" <corbet@....net>,
	"'Andrew Morton'" <akpm@...l.org>,
	"'Martin Bligh'" <mbligh@...igh.org>,
	"'Michael K. Edwards'" <medwards.linux@...il.com>,
	<linux-kernel@...r.kernel.org>
Subject: RE: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19]

I'd suggest putting a Documentation/GPL-Symbols to explain this.

Then in the "tainted" message, have a pointer to that documentation. 

> -----Original Message-----
> From: linux-kernel-owner@...r.kernel.org 
> [mailto:linux-kernel-owner@...r.kernel.org] On Behalf Of Scott Preece
> Sent: Thursday, December 14, 2006 11:43 AM
> To: Chris Wedgwood
> Cc: Eric Sandeen; Christoph Hellwig; Linus Torvalds; Jeff 
> Garzik; Greg KH; Jonathan Corbet; Andrew Morton; Martin 
> Bligh; Michael K. Edwards; linux-kernel@...r.kernel.org
> Subject: Re: GPL only modules [was Re: [GIT PATCH] more 
> Driver core patches for 2.6.19]
> 
> On 12/14/06, Chris Wedgwood <cw@...f.org> wrote:
> > On Thu, Dec 14, 2006 at 12:15:20PM -0600, Eric Sandeen wrote:
> >
> > > Please don't use that name, it strikes me as much more confusing 
> > > than EXPORT_SYMBOL_GPL, even though I agree that _GPL 
> doesn't quite 
> > > convey what it means, either.
> >
> > Calling internal symbols _INTERNAL is confusing?
> 
> I think it's the combination of "INTERNAL" and "EXPORT" that 
> seems contradictory - "If it's internal, why are you exporting it?"
> 
> I think "EXPORT_SYMBOL_GPL_ONLY" or "...ONLY UNDER_GPL" would 
> make the meaning clearer, but I don't really think the gain 
> is worth the pain.
> Anybody using kernel interfaces ought to be able to figure it out.
> 
> >
> > But those symbols aren't, they're about internal interfaces 
> that might 
> > change.
> 
> Folks who think this is likely to make a difference in court 
> might want to look at 
> <http:www.linuxworld.com/news/2006/120806-closed-modules2.html
> > for a litany of court cases that have rejected infringement 
> claims where a much sterner effort had been made to hide or 
> block use of interfaces.
> The article claims that courts have increasingly found that 
> interfacing your code to an existing work is not 
> infringement, regardless of what you have to work around to do it.
> 
> Of course, that's one author's reading of the case law and 
> I'm sure there are others who disagree, but it's something 
> you'd want to keep in mind in calculating the expected value 
> of a suit...
> 
> scott
> -
> 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/

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