linux-kernel - Re: LIO - the broken iSCSI target implementation

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: <50F8AB33.5010003@vlnb.net>
Date:	Thu, 17 Jan 2013 20:53:55 -0500
From:	Vladislav Bolkhovitin <vst@...b.net>
To:	Andreas Steinmetz <ast@...dv.de>
CC:	linux-kernel@...r.kernel.org, hch@...radead.org,
	torvalds@...ux-foundation.org
Subject: Re: LIO - the broken iSCSI target implementation


Andreas Steinmetz, on 01/16/2013 08:19 PM wrote:
> Thus, lio (http://www.linux-iscsi.org/) seemed to be the politically and
> technically favoured solution.

[...]

> The fun part of it was that I finally ended up using SCST - which was
> refrained from kernel inclusion for technical reasons beyond my
> knowledge.

No, it was purely political. There has never been any technical argument why LIO 
is better. And can not be.

Thanks,
Vlad

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