Skip to contentSkip to conversation

changing EXPORT_SYMBOL_GPL to EXPORT_SYMBOL in DD-WRT

DISCUSSION Armijn Hemel 3 participants 3 messages Mar 3, 2011 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

hello Sebastian,

I noticed that a few hours ago you changed a few lines in the kernel source of DD-WRT, changing the export from a few symbols from 'GPL only' to something a lot more permissive:

http://svn.dd-wrt.com:8000/changeset/16368

As you are probably aware the EXPORT_SYMBOL_GPL macro is there to clearly signal that it was the author's intent to make these symbols only available to GPL licensed kernel modules. What you have effectively done is ignore the author's intent. It also might end up in DD-WRT derivatives.

I am sure that this is not what you meant to do. The commit message indicates that you are working around a certain problem you are facing with DD-WRT. I am sure that the Linux kernel developers would love to hear about that problem. For your convenience I have put them in CC.

warm regards,

armijn

Signature · 3 lines
 ---------------------------------------------------------------------------
        [email protected] || http://www.gpl-violations.org/
 ---------------------------------------------------------------------------
#1 lore raw

Hi Sebastian, Armijn and others,

I can only follow what Armijn has been writing.

Quoted 3 lines · Armijn Hemel

I noticed that a few hours ago you changed a few lines in the kernel source of DD-WRT, changing the export from a few symbols from 'GPL only' to something a lot more permissive:

While the ideas and thoughts regarding the legal implications of EXPORT_SYMBOL_GPL are wide (see e.g. http://lwn.net/Articles/154602/) and there is no precedent as far as I know, there seems general consensus that it _at least_ signifies the explicit intent of the author.

By using the _GPL variant, the author unmistakingly indicates:
"I consider any use of that symbol to create a derivative work which must again
be licensed under GNU GPL"

So by modifying a _GPL symbol into the non-GPL variant (and using the code from a non-GPL module), one would clearly violate the intent of the original author. Whether or not that intent of the author is grounded in copyright law may depend on the specific jurisdiction, circumstances and the judge that would make up his mind about it, if such a case ever went to court.

I would be interested to hear what DaveM, James Morris and Herbert Xu as the authors of the files in question have to say about such activity.

Regards,
Harald

Signature · 4 lines
- Harald Welte <[email protected]>       http://gpl-violations.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

Hi alltogether,

http://svn.dd-wrt.com:8000/changeset/16371
http://svn.dd-wrt.com:8000/changeset/16372

we discussed this internally and found a solution that does not need this change anymore.

The problematic code did not end up in any distributed binary.

Thanks for bringing this issue to our attention.

If you have any further comments or question, please don't hesitate to contact me.

Signature · 11 lines
Mit freundlichen Grüssen / Regards

Christian Scheele

NewMedia-NET GmbH
Firmensitz:  Berliner Ring 101, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.newmedia-net.de / http://www.dd-wrt.com
email: [email protected]
Tel.: +496251-582650 / Fax: +496251-5826565
Quoted 71 lines · Sebastian Gottschall (DD-WRT)

The Problem source is easy. i migrated a new compiler which is Linaro 4.5.2 and this compiler inlines various function which have been not inlined in my previous compiler which was 4.3.3
so i was running into this symbol problems newly today with the Atheros 802.11n LSDK Driver.
For example. the symbol init_uts_ns is declared as GPL only. originally a function was used which returned this symbol. this worked in the past. but since this function is marked as inline, the symbol is now directly compiled into
the driver which raised a compile problem.

we are also migrating to ath9k in background, but we still need to develop alot of features to ath9k until we can use it as our current modified LSDK driver.
so i needed to work around this problem today, to keep everything working in my sourcetree

i hope you understand the problem in my side. it would remain just as temporarily solution until i fixed that problem in another way. for the init_uts_ns problem there is a solution right now. but for the crypto api i'm still looking for. normally i can avoid this by removing the soft crypto code which isnt used by newer hardware
but for backward compatiblity with older chipsets, they need to remain

regards,
Sebastian Gottschall
Am 03.03.2011 16:23, schrieb Harald Welte:

Quoted 23 lines

Hi Sebastian, Armijn and others,

I can only follow what Armijn has been writing.

Quoted 3 lines · Armijn Hemel

I noticed that a few hours ago you changed a few lines in the kernel source of DD-WRT, changing the export from a few symbols from 'GPL only' to something a lot more permissive:

While the ideas and thoughts regarding the legal implications of EXPORT_SYMBOL_GPL are wide (see e.g.http://lwn.net/Articles/154602/) and there is no precedent as far as I know, there seems general consensus that it _at least_ signifies the explicit intent of the author.

By using the _GPL variant, the author unmistakingly indicates:
"I consider any use of that symbol to create a derivative work which must again
be licensed under GNU GPL"

So by modifying a _GPL symbol into the non-GPL variant (and using the code from a non-GPL module), one would clearly violate the intent of the original author. Whether or not that intent of the author is grounded in copyright law may depend on the specific jurisdiction, circumstances and the judge that would make up his mind about it, if such a case ever went to court.

Quoted 5 lines

I would be interested to hear what DaveM, James Morris and Herbert Xu as the authors of the files in question have to say about such activity.

Regards,
Harald

--
Mit freundlichen Grüssen / Regards

Sebastian Gottschall / CTO

NewMedia-NET GmbH - DD-WRT
Firmensitz: Berliner Ring 101, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473 Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email:[email protected]
Tel.: +496251-582650 / Fax: +496251-5826565