linux-kernel - Re: [PATCH] compat: makes all compat symbols EXPORT_SYMBOL

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]

Message-ID: <4F5489EE.20203@broadcom.com>
Date:	Mon, 5 Mar 2012 10:39:58 +0100
From:	"Arend van Spriel" <arend@...adcom.com>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
cc:	"Luis R. Rodriguez" <mcgrof@...jolero.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] compat: makes all compat symbols
 EXPORT_SYMBOL_GPL()

On 03/03/2012 05:15 PM, Alan Cox wrote:
>> Some of the modules in this patch are dual-licensed. I was under the
>> impression that EXPORT_SYMBOL_GPL was specifically for GPL-only code
>> although I could not find any specifics in the Documentation folder. Do
>> you (or someone else) have a reference on this topic?
>
> If your code is licensed GPL or greater rights then you shouldn't have a
> problem. The module loader recognizes
>
> 	"GPL"
> 	"GPL v2"
> 	"GPL and additional rights"
> 	"Dual BSD/GPL"
> 	"Dual MIT/GPL"
> 	"DUal MPL/GPL"
>
> as legitimate users of _GPL. Any work which is derivative of the kernel
> (which in practise I suspect means almost any module) will need a GPL
> compatible licence anyway.
>

Hi, Alan

I found the list above in module.h, but was not sure whether it was ok 
to use _GPL for dual license. Thanks for clarifying this.

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/