[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <509BE45E.6010309@redhat.com>
Date: Thu, 08 Nov 2012 08:57:02 -0800
From: Andy Grover <agrover@...hat.com>
To: Jon Mason <jdmason@...zu.us>
CC: "Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
target-devel <target-devel@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Marc Fleischmann <mwf@...ingtidesystems.com>,
Nicholas Bellinger <nab@...ingtidesystems.com>
Subject: Re: scsi target, likely GPL violation
On 11/07/2012 05:02 PM, Jon Mason wrote:
> On Wed, Nov 7, 2012 at 9:50 AM, Andy Grover <agrover@...hat.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists