[PATCH 0/5] target: Add se_session->sess_kref + convert iscsi/qla2xxx fabrics

["Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>]

From: Nicholas Bellinger <nab@xxxxxxxxxxxxxxx>

Hi folks,

This series is a WIP for adding se_session->sess_kref into target core to
address a long standing set of issues wrt to active session shutdown and
explict NodeACL group configuration.

This includes changing iscsi-target to co-exist with internal reference
counting, and converting qla2xxx internal qla_tgt_sess->sess_kref to use
se_session->sess_kref for all cases.  It also re-factors qla_tgt_sess
shutdown -> release code to run outside of qla_hw_data->hardware_lock +
interrupt execution using system_wq process context.

So far the changes have been tested with normal session creation/deletion
for iscsi-target, loopback, tcm_fc(fcoe) and qla2xxx WWPNs, but need
more testing with active I/O shutdown.  Please have a look..

Thanks,

--nab

Nicholas Bellinger (5):
  target: Add se_sess->sess_kref + get/put helpers
  target: Add se_node_acl->acl_free_comp for NodeACL release path
  target: Make dynamic NodeACL shutdown clear comp_nacl bit
  iscsi-target: Convert to use target_put_session + sess_kref
  qla_target/tcm_qla2xxx: Convert to use target_put_session + sess_kref

 drivers/scsi/qla2xxx/qla_target.c            |  121 +++++++++-----------------
 drivers/scsi/qla2xxx/qla_target.h            |    9 +-
 drivers/scsi/qla2xxx/tcm_qla2xxx.c           |   71 +++++++--------
 drivers/target/iscsi/iscsi_target.c          |    6 +-
 drivers/target/iscsi/iscsi_target_configfs.c |    6 +-
 drivers/target/iscsi/iscsi_target_login.c    |    6 +-
 drivers/target/target_core_tpg.c             |   23 +++---
 drivers/target/target_core_transport.c       |   62 ++++++++++----
 include/target/target_core_base.h            |    2 +
 include/target/target_core_fabric.h          |    2 +
 10 files changed, 152 insertions(+), 156 deletions(-)

-- 
1.7.2.5

--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html