netdev - Re: [RFC PATCH 0/4] Make iSCSI network namespace aware

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]

Date:	Thu, 21 May 2015 11:04:46 +0200
From:	Hannes Reinecke <hare@...e.de>
To:	Andy Grover <agrover@...hat.com>, open-iscsi@...glegroups.com,
	linux-scsi@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [RFC PATCH 0/4] Make iSCSI network namespace aware

On 05/20/2015 08:45 PM, Andy Grover wrote:
> On 05/13/2015 03:12 PM, Chris Leech wrote:
>> This is only about the structures and functionality involved in
>> maintaining the
>> iSCSI session, the SCSI host along with it's discovered targets
>> and devices has
>> no association with network namespaces.
>>
>> These patches are functional, but not complete.  There's no
>> isolation enforced
>> in the kernel just yet, so it relies on well behaved userspace.  I
>> plan on
>> fixing that, but wanted some feedback on the idea and approach so
>> far.
> 
> Seems like a good direction, to me.
> 
> What would be the extent of the userspace (open-iscsi) changes
> needed to go along with this?
> 
What I would like to see is to split off iscsid to have one
instance/process per session.
With that we could trivially run open-iscsi in containers and
stufflike; currently it'll be hard as there really is only one
iscsid expected to be running in a system.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare@...e.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html