linux-kernel - Re: Integration of SCST in the mainstream Linux kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1201867517.11265.294.camel@haakon2.linux-iscsi.org>
Date:	Fri, 01 Feb 2008 04:05:17 -0800
From:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To:	Bart Van Assche <bart.vanassche@...il.com>
Cc:	FUJITA Tomonori <tomof@....org>, fujita.tomonori@....ntt.co.jp,
	rdreier@...co.com, James.Bottomley@...senpartnership.com,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	vst@...b.net, linux-scsi@...r.kernel.org,
	scst-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	Mike Mazarick <mazarick@...lsouth.net>
Subject: Re: Integration of SCST in the mainstream Linux kernel

On Fri, 2008-02-01 at 12:04 +0100, Bart Van Assche wrote:
> On Feb 1, 2008 11:39 AM, Nicholas A. Bellinger <nab@...ux-iscsi.org> wrote:
> >
> > On Fri, 2008-02-01 at 09:11 +0100, Bart Van Assche wrote:
> > > On Jan 31, 2008 2:25 PM, Nicholas A. Bellinger <nab@...ux-iscsi.org> wrote:
> > > >
> > > > The PyX storage engine supports a scatterlist linked list algorithm that
> > > > ...
> > >
> > > Which parts of the PyX source code are licensed under the GPL and
> > > which parts are closed source ? A Google query for PyX + iSCSI showed
> > > information about licensing deals. Licensing deals can only be closed
> > > for software that is not entirely licensed under the GPL.
> > >
> >
> > I was using the name PyX to give an historical context to the
> > discussion. ...
> 
> Regarding the PyX Target Code: I have found a link via which I can
> download a free 30-day demo. This means that a company is earning
> money via this target code and that the source code is not licensed
> under the GPL. This is fine, but it also means that today the PyX
> target code is not a candidate for inclusion in the Linux kernel, and
> that it is unlikely that all of the PyX target code (kernelspace +
> userspace) will be made available under GPL soon.
> 

All of the kernel and C userspace code is open source and available from
linux-iscsi.org and licensed under the GPL.  There is the BSD licensed
code from userspace (iSNS), as well as ISCSI and SCSI MIBs.  As for what
pieces of code will be going upstream (for kernel and/or userspace), LIO
Target state machines and SE algoritims are definately some of the best
examples of GPL code for production IP storage fabric and has gained
maturity from people and resources applied to it in a number of
respects.

The LIO stack presents a number of possible options to get the diverse
amount of hardware and software to work.  Completely dismissing the
available code is certainly a waste, and there are still significant
amounts of functionality related to real-time administration, RFC-3720
MC/S and ERL=2 and generic SE functionality OS storage subsystems that
only exist in LIO and our assoicated projects.  A one obvious example is
the LIO-VM project, which brings LIO active-active transport recovery
and other Linux storage functionality to Vmware and Qemu images that can
provide target mode IP storage fabric on x86 non-linux based hosts.  A
first of its kind in the Linux/iSCSI universe.  

Anyways, lets get back to the technical discussion.

--nab

> Bart Van Assche.
> 

--
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/