From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mike Snitzer <snitzer@redhat.com>
Cc: James.Bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
Chandra Seetharaman <sekharan@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] [SCSI] scsi_dh: change scsi_dh_detach export to EXPORT_SYMBOL
Date: Mon, 23 Apr 2012 00:13:06 +0100 [thread overview]
Message-ID: <20120423001306.040c512b@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120422230156.GA25181@redhat.com>
> Anyway, your no compromises approach is admirable but it doesn't erase
> the fact that all proprietary Linux drivers use EXPORT_SYMBOL code.
People still steal from shops. It doesn't mean we should abolish the idea
of theft.
> So what you're really saying is no proprietary drivers are allowed to be
> loaded into a Linux kernel.
The GPL defines the boundary. Whether it is possible for a work to be
non-derivative and a kernel module is a matter for the lawyers to debate.
If it is derivative however I don't think there is quite so much doubt.
Linus wrote the following
|>"On Wed, 3 Dec 2003, Kendall Bennett wrote:
|>
|> I have heard many people reference the fact that the although the Linux
|> Kernel is under the GNU GPL license, that the code is licensed with an
|> exception clause that says binary loadable modules do not have to be
|> under the GPL.
|
|Nope. No such exception exists.
|
|There's a clarification that user-space programs that use the standard
|system call interfaces aren't considered derived works, but even that
|isn't an "exception" - it's just a statement of a border of what is
|clearly considered a "derived work". User programs are _clearly_ not
|derived works of the kernel, and as such whatever the kernel license is
|just doesn't matter.
|
|And in fact, when it comes to modules, the GPL issue is exactly the same.
|The kernel _is_ GPL. No ifs, buts and maybe's about it. As a result,
|anything that is a derived work has to be GPL'd. It's that simple.
(and then goes on to discuss further his own personal opinion)
http://kerneltrap.org/node/1735
But you still misunderstand the fundamental problem, and this really
needs to be discussed with Red Hat legal.
Alan
prev parent reply other threads:[~2012-04-22 23:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111215214440.GA17677@redhat.com>
[not found] ` <4EF039D5.5010201@suse.de>
[not found] ` <20120405144721.GA18437@redhat.com>
2012-04-20 14:45 ` [RESEND][PATCH] [SCSI] scsi_dh: allow 3rd party multipath drivers to use scsi_dh_detach Mike Snitzer
2012-04-20 15:17 ` James Bottomley
2012-04-20 15:46 ` Mike Snitzer
2012-04-20 15:49 ` Chandra Seetharaman
2012-04-20 17:34 ` [PATCH v2] [SCSI] scsi_dh: change scsi_dh_detach export to EXPORT_SYMBOL Mike Snitzer
2012-04-20 20:41 ` Alan Cox
2012-04-20 21:58 ` Mike Snitzer
2012-04-20 22:20 ` Alan Cox
2012-04-20 22:58 ` Mike Snitzer
2012-04-20 23:14 ` Alan Cox
2012-04-20 23:34 ` Mike Snitzer
2012-04-22 22:13 ` Mike Snitzer
2012-04-22 22:34 ` Alan Cox
2012-04-22 23:01 ` Mike Snitzer
2012-04-22 23:13 ` Alan Cox [this message]
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=20120423001306.040c512b@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sekharan@us.ibm.com \
--cc=snitzer@redhat.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
all inboxes | Powered by JetHome®