All of lore.kernel.org
 help / color / mirror / Atom feed
From: Crispin Cowan <crispin@wirex.com>
To: Greg KH <greg@kroah.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make LSM register functions GPLonly exports
Date: Thu, 17 Oct 2002 09:51:06 -0700	[thread overview]
Message-ID: <3DAEEA7A.6000803@wirex.com> (raw)
In-Reply-To: 20021017150740.GA31056@kroah.com

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

Greg KH wrote:

>On Thu, Oct 17, 2002 at 03:35:05PM +0100, Christoph Hellwig wrote:
>  
>
>>These exports have the power to change the implementations of all
>>syscalls and I've seen people exploiting this "feature".
>>
>>Make the exports GPLonly (which some LSM folks agreed to
>>when it was merged initially to avoid that).
>>    
>>
>I would really, really, really like to make this change.  Unfortunatly,
>one of the current copyright holders of this file does not agree with
>it.
>
>Crispin, for the benifit of the lkml readers, can you explain why WireX
>does not want this change?
>
Here's the monster flame-war we had the last time this issue was debated 
http://www.uwsg.iu.edu/hypermail/linux/kernel/0109.3/0102.html

My argument against the intent of this change is that no, I do not think 
we should restrict LSM modules to be GPL-only. LSM is an API for loading 
externally developed packages of software, similar to syscalls. There is 
benefit in permitting proprietary modules (you get additional modules 
that you would not get otherwise) just as there is benefit in permitting 
proprietary applications (you get Oracle, DB2, and WordPerfect).

My argument against the implementation technique of dropping in these 
export GPLonly symbols is that my read of the GPL itself means that they 
have no legal impact. The crux of the matter is whether a *court* finds 
that LSM is "linking" (in the GPL sense) or is an "interface":

    * If it is "linking": then all LSM modules end up GPL'd, regardless
      of what any of us want.
    * If it is "an interface": then the GPL specifically *prohibits* you
      from imposing additional restrictions, such as requiring someone
      else's module to be GPL'd, to wit:
          o Clause 4: "You may not copy, modify, sublicense, or
            distribute the Program except as expressly provided under
            this License."
          o Clause 6: "... You may not impose any further restrictions
            on the recipients' exercise of the rights granted herein."

Therefore, the EXPORT_SYMBOL_GPL is just a bunch of useless bloat, with 
no legal standing what so ever. If kernel module interfaces are held by 
a court to be linking, then export symbols are redundant. If kernel 
module interfaces are held by a court to be an interface, then the 
export symbols are just wrong.

Crispin

-- 
Crispin Cowan, Ph.D.
Chief Scientist, WireX                      http://wirex.com/~crispin/
Security Hardened Linux Distribution:       http://immunix.org
Available for purchase: http://wirex.com/Products/Immunix/purchase.html


[-- Attachment #2: Type: application/pgp-signature, Size: 252 bytes --]

  parent reply	other threads:[~2002-10-17 16:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 14:35 [PATCH] make LSM register functions GPLonly exports Christoph Hellwig
2002-10-17 15:07 ` Greg KH
2002-10-17 15:13   ` Christoph Hellwig
2002-10-17 16:21   ` Jeff Garzik
2002-10-17 16:51   ` Crispin Cowan [this message]
2002-10-17 16:54     ` Christoph Hellwig
2002-10-17 17:08       ` Linus Torvalds
2002-10-17 17:20         ` Greg KH
2002-10-17 17:25         ` Linus Torvalds
2002-10-17 20:39           ` Ingo Molnar
2002-10-17 17:44         ` Crispin Cowan
2002-10-17 18:03           ` Arjan van de Ven
2002-10-17 17:20       ` Richard B. Johnson
2002-10-17 17:26         ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DAEEA7A.6000803@wirex.com \
    --to=crispin@wirex.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.