diff options
author | Michael Brown | 2017-05-03 14:01:11 +0200 |
---|---|---|
committer | Michael Brown | 2017-05-03 14:01:11 +0200 |
commit | 785389c2ba84870e003c23304ca88aa4ec1f144d (patch) | |
tree | b1a9f1c2c8181254df89f9f7d02be85d9e533921 /src/drivers | |
parent | [efi] Standardise PCI debug messages (diff) | |
download | ipxe-785389c2ba84870e003c23304ca88aa4ec1f144d.tar.gz ipxe-785389c2ba84870e003c23304ca88aa4ec1f144d.tar.xz ipxe-785389c2ba84870e003c23304ca88aa4ec1f144d.zip |
[iscsi] Always send FirstBurstLength parameter
As of kernel 4.11, the LIO target will propose a value for
FirstBurstLength if the initiator did not do so. This is entirely
redundant in our case, since FirstBurstLength is defined by RFC 3720
to be
"Irrelevant when: ( InitialR2T=Yes and ImmediateData=No )"
and we already enforce both InitialR2T=Yes and ImmediateData=No in our
initial proposal. However, LIO (arguably correctly) complains when we
do not respond to its redundant proposal of an already-irrelevant
value.
Fix by always proposing the default value for FirstBurstLength.
Debugged-by: Patrick Seeburger <info@8bit.de>
Tested-by: Patrick Seeburger <info@8bit.de>
Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'src/drivers')
0 files changed, 0 insertions, 0 deletions