EXPORT_SYMBOL_GPL with GPLv3

EXPORT_SYMBOL_GPL with GPLv3

[Werner Sembach]

Hi,

asking at the source: Can EXPORT_SYMBOL_GPL-exports be used with out of tree 
GPLv3 licensed modules?

- EXPORT_SYMBOL_GPL is documented here 
https://www.kernel.org/doc/html/latest/kernel-hacking/hacking.html#export-symbol-gpl 
but this only mentions "GPL" without specifying v2 or v3

- This LWN article only talking about "GPL-compatible" with no version given and 
that was written before the v3 was released: https://lwn.net/Articles/154602/

- This docs page 
https://www.kernel.org/doc/html/latest/process/license-rules.html#id1 defining 
MODULE_LICENSE(“GPL”) as GPL v2, but does not define MODULE_LICENSE(“GPL v3”) 
nor what is and isn't allowed with it

Kind regards,

Werner Sembach

Re: EXPORT_SYMBOL_GPL with GPLv3

[Christoph Hellwig]

On Mon, Nov 11, 2024 at 07:40:25PM +0100, Werner Sembach wrote:
> Hi,
> 
> asking at the source: Can EXPORT_SYMBOL_GPL-exports be used with out of tree
> GPLv3 licensed modules?

No.  The kernel as whole is licencsed as GPLv2, not GPLv2+.

Re: EXPORT_SYMBOL_GPL with GPLv3

[Werner Sembach]

Hi,

Am 12.11.24 um 06:00 schrieb Christoph Hellwig:
> On Mon, Nov 11, 2024 at 07:40:25PM +0100, Werner Sembach wrote:
>> Hi,
>>
>> asking at the source: Can EXPORT_SYMBOL_GPL-exports be used with out of tree
>> GPLv3 licensed modules?
> No.  The kernel as whole is licencsed as GPLv2, not GPLv2+.
>
Yes, but the documentation for EXPORT_SYMBOL_GPL only talks about 
"GPL-compatible" and external linking for EXPORT_SYMBOL-exports is even legal 
with proprietary code. So to my understanding, it comes down to what 
EXPORT_SYMBOL_GPL means and not what's the license of the code behind it is.

Kind Regards,

Werner Sembach

Re: EXPORT_SYMBOL_GPL with GPLv3

[Uwe Kleine-König]

[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]

Hello Werner,

On Tue, Nov 12, 2024 at 09:34:29AM +0100, Werner Sembach wrote:
> Am 12.11.24 um 06:00 schrieb Christoph Hellwig:
> > On Mon, Nov 11, 2024 at 07:40:25PM +0100, Werner Sembach wrote:
> > > Hi,
> > > 
> > > asking at the source: Can EXPORT_SYMBOL_GPL-exports be used with out of tree
> > > GPLv3 licensed modules?
> > No.  The kernel as whole is licencsed as GPLv2, not GPLv2+.
>
> Yes, but the documentation for EXPORT_SYMBOL_GPL only talks about
> "GPL-compatible" and external linking for EXPORT_SYMBOL-exports is even
> legal with proprietary code.

AFAIK there is no agreement about the legality of proprietary code using
symbols published with EXPORT_SYMBOL. EXPORT_SYMBOL_GPL was created with
the intend to at least have a way to express a symbol to be used by
GPL(v2) code only.

So the safe assumption about EXPORT_SYMBOL functions and variables is
only: "The copyright holder did not expressively prohibit proprietary
callers. This might be because they are ok with proprietary callers,
but maybe they just didn't consider it necessary to share their
opinion.".

> So to my understanding, it comes down to what EXPORT_SYMBOL_GPL means
> and not what's the license of the code behind it is.

Here my approach to clearify the meaning:
https://lore.kernel.org/linux-kernel/20241115103842.585207-2-ukleinek@kernel.org

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]