> 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? 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.
> @@ -281,8 +281,6 @@ int iscsit_tpg_del_portal_group(
> return -EPERM;
> }
>
> - core_tpg_clear_object_luns(&tpg->tpg_se_tpg);
> -
How does the removal of tis function including it's only caller
in the iscsi code fiit into the picture? The only explanation I could come
up with is that it wasn't even needed before, in which case it should be
dropped in a seaprate, properly documented patch.
> +static void target_fabric_port_release(struct config_item *item)
> +{
> + struct se_lun *lun = container_of(to_config_group(item),
> + struct se_lun, lun_group);
> +
> + call_rcu(&lun->rcu_head, target_lun_callrcu);
Just use kfree_rcu here.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
