linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lawrence Rosen" <lrosen@rosenlaw.com>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	target-devel@vger.kernel.org
Cc: kcopenhaver@choate.com, Richard Fontana <rfontana@redhat.com>,
	Marc Fleischmann <mwf@risingtidesystems.com>,
	Nicholas Bellinger <nab@risingtidesystems.com>,
	alan@lxorguk.ukuu.org.uk, agrover@redhat.com,
	bkuhn@sfconservancy.org, tytso@mit.edu, lrosen@rosenlaw.com
Subject: RE: scsi target, likely GPL violation
Date: Sun, 11 Nov 2012 14:13:53 -0800	[thread overview]
Message-ID: <14c701cdc059$d6fd28b0$84f77a10$@rosenlaw.com> (raw)
In-Reply-To: <20121109110336.41833034@pyramind.ukuu.org.uk>

Alan Cox wrote:
> So either your work is truely not derivative of the kernel (which I find
> wildly improbable) or you have a problem and since you are aware 
> of the complaints publically I guess probably a triple damages sized 
> problem. But that's one for your lawyers and whatever opinion they 
> have on the subject.

Hi Alan and others,

I've been advising Rising Tide Systems (RTS) in this matter. Please let me
reassure you that RTS is acting on advice of counsel.

RTS (and specifically Nicholas Bellinger) wrote the scsi target code and
owns its copyright. We registered that copyright at the Library of Congress.
RTS contributed a version of the scsi target to Linux for distribution under
the GPL. On behalf of Marc Fleischmann, CEO of RTS, I can reassure you that
RTS remains committed to the Linux project and will continue to contribute
to it. We are pleased that RTS software is a part of the Linux distribution
under the GPL.

RTS also has a commercial software business. It distributes versions of its
scsi target code that support features and functions not officially in Linux
(or at least, not yet). That commercial RTS business includes the licensing
of those derivative works of its own code to its own customers. Nothing
whatsoever in the GPL or in the policies of the Linux Foundation prohibits
that.

I would also like to address some comments made on these lists by Andy
Grover and Bradley Kuhn. 

First, I hope that we can tone down the arguments about whether the use of
Linux APIs and headers automatically turns a program into a derivative work
of Linux. I think that argument has been largely debunked in the U.S. in the
recent decision in Oracle v. Google, and in Europe in SAS v. World
Programming. Does anyone here question whether the original work that RTS
contributed to Linux (and that *is* under the GPL) is an original work of
authorship of RTS despite the fact that it links to other GPL code using
headers and APIs?

Second, we are grateful for the efforts that Bradley Kuhn and others put in
to enforce the GPL. As I said above, RTS owns and has registered the
copyright on its scsi target and will enforce it if necessary. So Brad, we
may solicit your assistance if we find any third party who is distributing
an unauthorized non-GPL derivative work of the scsi target now in Linux.
RTS, of course, retains the exclusive right to do so, but no third party can
do so without a license from RTS.

Best regards,

/Larry

P.S. In accordance with my obligations as an attorney when communicating
with a represented person, I am copying attorneys for Red Hat and Linux
Foundation on this email.  If anyone wishes to respond to me, please copy me
directly since I am not subscribed to these lists.

Lawrence Rosen
Rosenlaw & Einschlag, a technology law firm (www.rosenlaw.com)
3001 King Ranch Rd., Ukiah, CA 95482
Office: 707-485-1242

  parent reply	other threads:[~2012-11-11 22:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07 16:50 scsi target, likely GPL violation Andy Grover
2012-11-08  1:02 ` Jon Mason
2012-11-08  1:57   ` Chris Friesen
2012-11-08 16:57     ` Andy Grover
2012-11-08 20:05       ` Nicholas A. Bellinger
2012-11-08 20:22         ` Dave Airlie
2012-11-08 21:22         ` Andy Grover
2012-11-09  2:08           ` Nicholas A. Bellinger
2012-11-09 11:03             ` Alan Cox
2012-11-09 19:52               ` Andy Grover
2012-11-09 20:26                 ` Alan Cox
2012-11-11 22:13               ` Lawrence Rosen [this message]
2012-11-11 22:41                 ` Julian Calaby
2012-11-11 23:03                   ` Dave Airlie
2012-11-12 14:21                 ` Bradley M. Kuhn
2012-11-15 18:21                 ` Andy Grover
2012-11-09 23:16             ` Andy Grover
2012-11-10 23:32             ` Bradley M. Kuhn
2012-11-08 16:57   ` Andy Grover
2012-11-11  9:34 ` James Bottomley
2012-11-11 13:05   ` Theodore Ts'o
2012-11-11 15:15     ` Bradley M. Kuhn
2012-11-11 18:22       ` James Bottomley
2012-11-11 18:32         ` Alan Cox
2012-11-14  2:32           ` James Bottomley
2012-11-12 14:08       ` Theodore Ts'o
2012-11-12 14:15         ` Alan Cox
2012-11-12  0:39   ` Douglas Gilbert

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='14c701cdc059$d6fd28b0$84f77a10$@rosenlaw.com' \
    --to=lrosen@rosenlaw.com \
    --cc=agrover@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bkuhn@sfconservancy.org \
    --cc=kcopenhaver@choate.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mwf@risingtidesystems.com \
    --cc=nab@risingtidesystems.com \
    --cc=rfontana@redhat.com \
    --cc=target-devel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).