summaryrefslogtreecommitdiffstats
path: root/drivers/target/target_core_transport.c
diff options
context:
space:
mode:
authorRoland Dreier <roland@purestorage.com>2014-10-14 14:16:24 -0700
committerNicholas Bellinger <nab@linux-iscsi.org>2014-10-28 13:54:15 -0700
commit885e7b0e181c14e4d0ddd26c688bad2b84c1ada9 (patch)
tree05b77664a7b7f13158c1d4e7da8b99be6387fb2b /drivers/target/target_core_transport.c
parentcac7f2429872d3733dc3f9915857b1691da2eb2f (diff)
downloadtalos-obmc-linux-885e7b0e181c14e4d0ddd26c688bad2b84c1ada9.tar.gz
talos-obmc-linux-885e7b0e181c14e4d0ddd26c688bad2b84c1ada9.zip
target: Don't call TFO->write_pending if data_length == 0
If an initiator sends a zero-length command (e.g. TEST UNIT READY) but sets the transfer direction in the transport layer to indicate a data-out phase, we still shouldn't try to transfer data. At best it's a NOP, and depending on the transport, we might crash on an uninitialized sg list. Reported-by: Craig Watson <craig.watson@vanguard-rugged.com> Signed-off-by: Roland Dreier <roland@purestorage.com> Cc: <stable@vger.kernel.org> # 3.1 Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'drivers/target/target_core_transport.c')
-rw-r--r--drivers/target/target_core_transport.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/target/target_core_transport.c b/drivers/target/target_core_transport.c
index 9ea0d5f03f7a..be877bf6f730 100644
--- a/drivers/target/target_core_transport.c
+++ b/drivers/target/target_core_transport.c
@@ -2292,7 +2292,7 @@ transport_generic_new_cmd(struct se_cmd *cmd)
* and let it call back once the write buffers are ready.
*/
target_add_to_state_list(cmd);
- if (cmd->data_direction != DMA_TO_DEVICE) {
+ if (cmd->data_direction != DMA_TO_DEVICE || cmd->data_length == 0) {
target_execute_cmd(cmd);
return 0;
}
OpenPOWER on IntegriCloud