linux-kernel - Re: [PATCH-v5 07/13] iscsi-target: Add iSCSI Login Negotiation + Parameter logic

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20110527084752T.fujita.tomonori@lab.ntt.co.jp>
Date:	Fri, 27 May 2011 08:47:52 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	nab@...ux-iscsi.org
Cc:	James.Bottomley@...senPartnership.com,
	fujita.tomonori@....ntt.co.jp, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org, hch@....de, hare@...e.de,
	agrover@...hat.com, michaelc@...wisc.edu, bharrosh@...asas.com,
	akpm@...ux-foundation.org, martin.svec@...er.cz,
	jxm@...ingtidesystems.com
Subject: Re: [PATCH-v5 07/13] iscsi-target: Add iSCSI Login Negotiation +
	Parameter logic

On Thu, 26 May 2011 16:28:10 -0700
"Nicholas A. Bellinger" <nab@...ux-iscsi.org> wrote:

> As we have discussed at length over the years, the split needs to be all
> userspace or all kernelspace, and when implementations start doing
> things in-between they quickly get painful to debug, maintain and
> extend.  I have no interest in trying to evolve this further when LIO

Sorry, I disagree. As I explained, once user space passes established nexuses
to kernel, kernel handles all. I don't think it's painful.


> from the default two cases provided in their series, but lets please,
> please avoid slipping yet another window here when we still have >= 15K
> LOC in three other HW target mode fabric drivers in flight for the next
> round

Why can't you push other fabric drivers before iSCSI one?
--
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/