[GIT PULL] target fixes for v3.13-rc5

From: Nicholas A. Bellinger
Date: Sat Dec 21 2013 - 21:38:42 EST


Hi Linus,

Here are the outstanding target pending fixes for v3.13-rc5.

Please go ahead and pull from:

git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master

Mostly minor items this time around, the most notable being a FILEIO
backend change to enforce hw_max_sectors based upon the current
block_size to address a bug where large sized I/Os (> 1M) where being
rejected.

Thank you,

--nab

Andy Grover (1):
target: Remove extra percpu_ref_init

Eric Seppanen (1):
iscsi-target: return -EINVAL on oversized configfs parameter

Nicholas Bellinger (5):
iscsi-target: Fix-up all zero data-length CDBs with R/W_BIT set
iscsi-target: Fix incorrect np->np_thread NULL assignment
iser-target: Move INIT_WORK setup into isert_create_device_ib_res
target/file: Update hw_max_sectors based on current block_size
qla2xxx: Fix scsi_host leak on qlt_lport_register callback failure

Roland Dreier (1):
target: Remove write-only stats fields and lock from struct
se_node_acl

Shivaram Upadhyayula (1):
qla2xxx: Fix schedule_delayed_work() for target timeout calculations

Wei Yongjun (1):
iser-target: fix error return code in isert_create_device_ib_res()

drivers/infiniband/ulp/isert/ib_isert.c | 22 +++++++++++++++------
drivers/scsi/qla2xxx/qla_target.c | 10 ++++++----
drivers/target/iscsi/iscsi_target.c | 27 +++++++++++++-------------
drivers/target/iscsi/iscsi_target_configfs.c | 3 ++-
drivers/target/iscsi/iscsi_target_login.c | 6 ------
drivers/target/target_core_device.c | 5 +++++
drivers/target/target_core_file.c | 8 ++++----
drivers/target/target_core_file.h | 5 ++++-
drivers/target/target_core_tpg.c | 10 +---------
include/target/target_core_base.h | 5 +----
10 files changed, 52 insertions(+), 49 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/