linux-kernel - Re: [PATCH] module: Clarify GPL-Compatible is OK

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: <4F8187B0.1000804@broadcom.com>
Date:	Sun, 8 Apr 2012 14:42:24 +0200
From:	"Arend van Spriel" <arend@...adcom.com>
To:	"Luis R. Rodriguez" <mcgrof@...jolero.org>
cc:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"rusty@...tcorp.com.au" <rusty@...tcorp.com.au>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Keith Packard" <keithp@...thp.com>,
	"Ralf Baechle" <ralf@...ux-mips.org>,
	"David Woodhouse" <dwmw2@...radead.org>,
	"Stephen Hemminger" <shemminger@...tta.com>,
	"John W. Linville" <linville@...driver.com>,
	"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
	"Ted Ts'o" <tytso@....edu>
Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK

On 04/07/2012 03:02 AM, Luis R. Rodriguez wrote:
> On Fri, Apr 6, 2012 at 5:51 PM, Luis R. Rodriguez<mcgrof@...jolero.org>  wrote:
>
>> 4) Use the patch and leave it to the person who wants to extract code
>> to figure out the exact module license.
>
> After some though I think this is the only approach possible. Consider
> ath5k which has files under difference licenses:
>
>    * Dual BSD/GPL
>    * GPL
>    * ISC
>
> The person taking code must check the header of each file.
>
>    Luis

I would say that regardless your patch the "your preferred adjective" 
license disclaimer in the source files trumps any MODULE_LICENSE value 
so checking the files is always a necessary step. It is the only place 
to look for the specific license information and it is on a per-file 
basis as stated above. MODULE_LICENSE clearly groups these so a 
generalization seems justified just for that.

So MODULE_LICENSE is really just about allowing EXPORT_SYMBOL_GPL or 
not. I admit that statement does not cover everything as the 
MODULE_LICENSE is part of the module information, but as said it may or 
may not cover a number of different licenses used within the module.

So this specific macro does not, or even should not, help people figure 
out the license. We could consider some other tagging of each and every 
source file and add some scripting support to do the task, but that will 
be one hell of a patch so I will forever deny suggesting it ;-)

Gr. AvS

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