Skip to contentSkip to conversation

MODULE_LICENSE and EXPORT_SYMBOL_GPL

DISCUSSION Roy Murphy 5 participants 6 messages Oct 18, 2001 – Oct 21, 2001

lore
Share & tools
lore

Roy Murphy

author
#0 lore raw

'Twas brillig when Keith Owens scrobe:

Quoted 7 lines

EXPORT_SYMBOL_GPL

Some kernel developers are unhappy with providing external interfaces to their code, only to see those interfaces being used by binary only modules. They view it as their work being appropriated. Whether you agree with that view or not is completely irrelevant, the person who owns the copyright decides how their work can be used.

The GPL takes its strength and power from Copyright Law. Copyright law allows certain exclusive rights to authors. Among these are:
distribution, public performance and the preparation of derivative works. Copyright Law (at least in the US) reserves certain rights to the Public, notably the right to make Fair Uses. Because of Fair Use, the statement above "the person who owns the copyright decides how their work can be used." is demonstrably false in a US Copyright context.

Some elements of authorship are copyrightable, other elements are not. One clear exception in US Copyright Law is "methods of operation" which are not copyrightable. The canonical example of this the pattern of a standard transmission shift. The pattern, intimately tied to the manner in which the device is used, has been standardized because its design could be copied and used by all manufacturers.

Exported interfaces are "methods of operation" in the sense of US Copyright Law. Copyright Law affords no protection to "methods of operation". The GPL, which gains its strength from Copyright Law, also has no rights in this area. If a GPLed module does not want other code using its interfaces, they should not be exported.

This is an example of overreaching copyright control which is just as aggregious as CSS on DVDs.

#1 lore raw
Quoted 6 lines

Exported interfaces are "methods of operation" in the sense of US Copyright Law. Copyright Law affords no protection to "methods of operation". The GPL, which gains its strength from Copyright Law, also has no rights in this area. If a GPLed module does not want other code using its interfaces, they should not be exported.

I think you're missing one thing: binary only modules are only allowed because of an exception license grant Linus made for functions that are marked EXPORT_SYMBOL(). EXPORT_SYMBOL_GPL() just says "not part of this exception grant"....

#2 lore raw
In reply to Roy Murphy
Quoted 11 lines · Arjan van de Ven
Quoted 6 lines

Exported interfaces are "methods of operation" in the sense of US Copyright Law. Copyright Law affords no protection to "methods of operation". The GPL, which gains its strength from Copyright Law, also has no rights in this area. If a GPLed module does not want other code using its interfaces, they should not be exported.

I think you're missing one thing: binary only modules are only allowed because of an exception license grant Linus made for functions that are marked EXPORT_SYMBOL(). EXPORT_SYMBOL_GPL() just says "not part of this exception grant"....

Fine. I (the hypothetical binary driver maker) will just make two modules -- one which is MODULE_LICENCEd GPL, and the other which is not. The first will re-export your interfaces as unrestricted ones which the second can use. Are we going to start insisting on a transitivity of this restriction? If so, then it's possible that a large number of interfaces might go...

I also think this is somewhat ridiculous. If I (the binary module maker) distribute a program which effectively replicates the functionality of insmod without the licence checking, and distribute that program with my module, am I violating any restrictions? I don't think so, since it's the end-user that ends up linking the kernel to the module. No linked products are actually distributed...

Signature · 4 lines
Taral <[email protected]>
This message is digitally signed. Please PGP encrypt mail to me.
"Any technology, no matter how primitive, is magic to those who don't
understand it." -- Florence Ambrose
#3 lore raw
Quoted 4 lines · [email protected] said:

Fine. I (the hypothetical binary driver maker) will just make two
modules -- one which is MODULE_LICENCEd GPL, and the other which is not. The first will re-export your interfaces as unrestricted ones which the second can use.

You seem to have missed the point that it is already considered to be unacceptable to add GPL'd code to the kernel, exporting functionality which is required for non-GPL'd modules.

--
dwmw2

#4 lore raw
In reply to Taral
Quoted 6 lines

I also think this is somewhat ridiculous. If I (the binary module maker) distribute a program which effectively replicates the functionality of insmod without the licence checking, and distribute that program with my module, am I violating any restrictions? I don't think so, since it's the end-user that ends up linking the kernel to the module. No linked products are actually distributed...

You are arguably obtaining services by deception, and possibly also violating a content management system.

However the MODULE_LICENSE isn't aimed at people like that. In fact I've had totally positive responses from people who ship well known binary modules and understand why we want them to get bugs related to their code.

The people bright enough to hack insmod generally are also bright enough to realise why its a bad idea.

Alan

#5 lore raw
In reply to Taral
Quoted 9 lines · Alan Cox

You are arguably obtaining services by deception, and possibly also violating a content management system.

However the MODULE_LICENSE isn't aimed at people like that. In fact I've had totally positive responses from people who ship well known binary modules and understand why we want them to get bugs related to their code.

The people bright enough to hack insmod generally are also bright enough to realise why its a bad idea.

I'm not arguing against MODULE_LICENSE. I'm arguing against EXPORT_SYMBOL_GPL. I fully agree with the person who mentioned that calling certain interfaces "restricted" and basing that restriction on the licence of the interface user is an abuse of copyright.

More reasonable would be to have header files that looked like this:

#ifndef GPL_COMPATIBLE_LICENSE
#error This header file is restricted to GPL-compatible code only. #endif

Signature · 4 lines
Taral <[email protected]>
This message is digitally signed. Please PGP encrypt mail to me.
"Any technology, no matter how primitive, is magic to those who don't
understand it." -- Florence Ambrose