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
| ||
|
Date: Wed, 13 May 2015 09:22:04 +0200 From: Juergen Gross <jgross@...e.com> To: Christoph Hellwig <hch@....de>, "Nicholas A. Bellinger" <nab@...erainc.com> CC: target-devel <target-devel@...r.kernel.org>, linux-scsi <linux-scsi@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>, Hannes Reinecke <hare@...e.de>, Sagi Grimberg <sagig@...lanox.com>, Nicholas Bellinger <nab@...ux-iscsi.org> Subject: Re: [PATCH 09/12] target: Convert se_portal_group->tpg_lun_list[] to RCU hlist On 05/13/2015 08:24 AM, Christoph Hellwig wrote: > >> FIXME: Figure out how sbp-target se_lun usage should work > > The Xen usage also looks really weird. Maybe Juergen can explain what > scsiback_add_translation_entry is trying to do? scsiback_add_translation_entry() makes the connection between a pvSCSI LUN configured by the xen tools in xenstore and a xen-scsiback target. The xen tools specify the pvSCSI LUN via <device>:<lun>, with <device> being either the WWN of the target or an alias of that target specified in config_fs. scsiback_add_translation_entry() searches all it's targets until a match is found and links the found tpg to the device specification of the xen guest. > Note that I think both > sbp and xen really should be working on node ACLs. Right now both > of them oly supported autogenerated ACLs, so in practice it doesn't > matter, but keeping the data structure use clean is a goal on it's own. I'd be fine with this, but I think I'll need some hints how to achieve this. I guess I have to specify .fabric_make_nodeacl and .fabric_drop_nodeacl like e.g. done in drivers/vhost/scsi.c ? Is there anything else I have to consider? Juergen -- 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/
Powered by blists - more mailing lists