TAINTED (Re: spinlocks, the GPL, and binary-only modules)

TAINTED (Re: spinlocks, the GPL, and binary-only modules)

[Andre Hedrick]

Greetings LKML,

There is an interesting paradox to now consider.

Now the folks who invisioned the process to "taint" a kernel have by
default given the rule of exemption to the use of binary only.  The very
process used to detect and determine "taint", has itself approved the use
of binary only!  If this was not the case, then the detection process
would have rejected the loading.  Since this in not the end result, the
claim is and will be made the headers and all api's are exempt, period.

The headers and api's are required to even obtain functionality.

The test for Tainted status below:

"Module                  Size  Used by    Tainted: P"

It allows/allowed a binary module to load.


If Linux is to truly only a GPL binary module friendly environment, then
it must enforce the rules.  Therefore it must forcablely reject the
attempt to load any and all binaries which are not GPL.  Regardless if the
license is commerial yet the source code is available.

Think long and hard before this step is taken, as it will crush the
viablity of Linux in many key places today and will delay future
deployment.

This shall force all distos to change policy and prevent the loading of
anything which is not GPL and they have the source code to ship.
Additionall

To this point, the issue is closed on the binary modules.

/*
 * The following license idents are currently accepted as indicating free
 * software modules
 *
 *      "GPL"                           [GNU Public License v2 or later]
 *      "GPL and additional rights"     [GNU Public License v2 rights and more]
 *      "Dual BSD/GPL"                  [GNU Public License v2 or BSD license choice]
 *      "Dual MPL/GPL"                  [GNU Public License v2 or Mozilla license choice]
 *
 * The following other idents are available
 *
 *      "Proprietary"                   [Non free products]
 *
 * There are dual licensed components, but when running with Linux it is the
 * GPL that is relevant so this is a non issue. Similarly LGPL linked with GPL
 * is a GPL combined work.
 *
 *
 * This exists for several reasons
 * 1.   So modinfo can show license info for users wanting to vet their setup
 *      is free
 * 2.   So the community can ignore bug reports including proprietary modules
 * 3.   So vendors can do likewise based on their own policies
 */

Again, this very file ./linux/include/linux/module.h grants permission for:
    "Proprietary"                   [Non free products]

Now disbute the kernel!

Cheers,

Andre Hedrick
LAD Storage Consulting Group

PS The issue which is not closed is the legal status of what is a derived
   work and what is an original work.  This shall be settled in court when
   it is challanged.

Re: TAINTED (Re: spinlocks, the GPL, and binary-only modules)

[Giacomo Catenazzi]

> If Linux is to truly only a GPL binary module friendly environment, then
> it must enforce the rules.  Therefore it must forcablely reject the
> attempt to load any and all binaries which are not GPL.  Regardless if the
> license is commerial yet the source code is available.
> 

Read GPL!
I can modify/create *private* and completly *non-free* code, and link to GPL,
legally. [I cannot distribute it, but kernel should not block me!]
  nvidia unfortunatly use this, to not to disclose the complete sources]
And I can use an other OSI approved license, GPL compatible,
but if it is not yet recognized by kernel? Should kernel include all free
licences strings?

ciao
	giacomo