linux-kernel - Re: [Iscsitarget-devel] [RFC] future IET development

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] [day] [month] [year] [list]

Message-Id: <1220246718.8763.31.camel@blackadder>
Date:	Mon, 01 Sep 2008 07:25:18 +0200
From:	Arne Redlich <agr@...erkom-dd.de>
To:	rae l <crquan@...il.com>
Cc:	"Ross S. W. Walker" <RWalker@...allion.com>,
	iscsitarget-devel <iscsitarget-devel@...ts.sourceforge.net>,
	linux-kernel@...r.kernel.org,
	unh-iscsi-checkins@...ts.sourceforge.net
Subject: Re: [Iscsitarget-devel] [RFC] future IET development

Am Montag, den 01.09.2008, 01:36 +0800 schrieb rae l:

> Have you read the Documentation/ of the kernel?
> Didn't you know the benefits of getting the kernel code into the main
> kernel tree?
> 
> Here is some reasons from Documentation/stable_api_nonsense.txt:

[...]

You can safely assume that we're aware of the benefits of having the
code in the kernel, but it will not happen. It does not make much sense
to merge an iSCSI target into the kernel when there are generic target
frameworks around that can also support different transports such as FC,
FCOE. So there's not the remotest chance of getting IET merged.

Currently there's already STGT code in the kernel. It's basically an
interface for kernel drivers such as FC, however most processing and
many drivers (iSCSI, iSER, FCOE, ...) are done in userspace. And there's
SCST. It also provides several transports and storage backends. It's
mostly implemented in kernel space. Recently there's some movement to
get it into the kernel.

If you're interested in more details just search the linux-scsi and the
respective project's list archives.

> Indeed, in sometimes I observed IET kernel module not very stable on
> the latest 2.6.26 and 27-rcX kernels, sometimes it's kernel oops
> after serveral stop-ietd-unload-ko-load-ko-start-ietd loops, but not
> always reproducible, I'm still tracing on it;

Please post the oops.

Thanks,
Arne

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