From: Andy Grover <agrover@redhat.com>
To: Jon Mason <jdmason@kudzu.us>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Marc Fleischmann <mwf@risingtidesystems.com>,
Nicholas Bellinger <nab@risingtidesystems.com>
Subject: Re: scsi target, likely GPL violation
Date: Thu, 08 Nov 2012 08:57:02 -0800 [thread overview]
Message-ID: <509BE45E.6010309@redhat.com> (raw)
In-Reply-To: <CAPoiz9wzx_NmuA1ty-U28MGiYr7XKCbDn_e0ZLmz=pNDCqwqFw@mail.gmail.com>
On 11/07/2012 05:02 PM, Jon Mason wrote:
> On Wed, Nov 7, 2012 at 9:50 AM, Andy Grover <agrover@redhat.com> wrote:
>> Your company appears to be shipping kernel features in RTS OS that are
>> not made available under the GPL, specifically support for the
>> EXTENDED_COPY and COMPARE_AND_WRITE SCSI commands, in order to claim
>> full Vmware vSphere 5 VAAI support.
>>
>> http://www.risingtidesystems.com/storage.html
>> http://www.linux-iscsi.org/wiki/VAAI
>>
>> Private emails to you and RTS CEO Marc Fleischmann have not elicited a
>> useful response.
>>
>> You are subsystem maintainer for the in-kernel SCSI target support
>> (drivers/target/*), and your company appears to be violating the GPL.
>
> The peanut gallery needs more information, as this is quite an
> incendiary claim to be making on a Linux kernel forum. How are they
> violating the GPL? I'm not a lawyer, nor do I play one on TV, but if
> I understand the GPL correctly, RTS only needs to provide the relevant
> source to their customers upon request. Are there customers (perhaps
> Redhat) that they have not provided this to? If so, then they need to
> be publicly shamed (gpl-violations.org would be a good place to go as
> well). If not, then they are within their rights to behave the way
> they are currently behaving.
>
> Again, we need more info before we start flinging the tomatoes at them.
Look at the marketing material on their website. They demonstrate how
RTS OS fully implements vSphere 5 VAAI features. We know to a very high
certainty that this must have been implemented with kernel code, so
therefore this must be a GPL violation, since these changes have not
been made public.
-- Andy
next prev parent reply other threads:[~2012-11-08 16:57 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
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 [this message]
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=509BE45E.6010309@redhat.com \
--to=agrover@redhat.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mwf@risingtidesystems.com \
--cc=nab@linux-iscsi.org \
--cc=nab@risingtidesystems.com \
--cc=target-devel@vger.kernel.org \
/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).