aboutsummaryrefslogtreecommitdiffstats
path: root/src/include/ipxe/iscsi.h
diff options
context:
space:
mode:
authorMichael Brown <mcb30@ipxe.org>2012-03-01 16:26:38 +0000
committerMichael Brown <mcb30@ipxe.org>2012-03-01 16:33:05 +0000
commit1d293776ea290ae1f4d1228f3278030facf97a4b (patch)
treec58bcf0708a3c8074cca8f77fb4b6c310b883178 /src/include/ipxe/iscsi.h
parentcb10137e1992ba8fcd035b228a6a58ba3b40c3a2 (diff)
downloadipxe-1d293776ea290ae1f4d1228f3278030facf97a4b.tar.gz
[iscsi] Send any padding inline with the data segment
Some iSCSI targets respond to a PDU before receiving the padding bytes. If the target responds quickly enough, this can cause iPXE to start processing a new TX PDU before the padding bytes have been sent, which results in a protocol violation. Fix by always transmitting the padding bytes along with the data segment. Originally-fixed-by: Shyam Iyer <shyam_iyer@dell.com> Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'src/include/ipxe/iscsi.h')
-rw-r--r--src/include/ipxe/iscsi.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/src/include/ipxe/iscsi.h b/src/include/ipxe/iscsi.h
index 5d3d73b0c..b4de793a4 100644
--- a/src/include/ipxe/iscsi.h
+++ b/src/include/ipxe/iscsi.h
@@ -515,8 +515,6 @@ enum iscsi_tx_state {
ISCSI_TX_AHS,
/** Sending the data segment */
ISCSI_TX_DATA,
- /** Sending the data segment padding */
- ISCSI_TX_DATA_PADDING,
};
/** State of an iSCSI RX engine */