From: Christoph Hellwig <hch@infradead.org>
To: Crispin Cowan <crispin@wirex.com>
Cc: Greg KH <greg@kroah.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make LSM register functions GPLonly exports
Date: Thu, 17 Oct 2002 17:54:03 +0100 [thread overview]
Message-ID: <20021017175403.A32516@infradead.org> (raw)
In-Reply-To: <3DAEEA7A.6000803@wirex.com>; from crispin@wirex.com on Thu, Oct 17, 2002 at 09:51:06AM -0700
On Thu, Oct 17, 2002 at 09:51:06AM -0700, Crispin Cowan wrote:
> 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 arguement is that I want this flag as a hint for authors of
propritary security modules that I'm going to sue them if they
use hook called from code I have copyright on. This includes such
central parts as vfs_read/vfs_write.
> 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.
It's a very clear hint, and very usefull as such.
next prev parent reply other threads:[~2002-10-17 16:48 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
2002-10-17 16:54 ` Christoph Hellwig [this message]
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=20021017175403.A32516@infradead.org \
--to=hch@infradead.org \
--cc=crispin@wirex.com \
--cc=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox