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>tags/v1.20.1
|
|
||
644 |
|
644 |
|
645 |
|
645 |
|
646 |
|
646 |
|
647 |
|
|
|
|
647 |
|
|
648 |
|
648 |
|
649 |
|
|
|
|
649 |
|
|
650 |
|
650 |
|
651 |
|
651 |
|
652 |
|
|
|
|
652 |
|
|
653 |
|
653 |
|
654 |
|
654 |
|
655 |
|
655 |
|
|
|
||
674 |
|
674 |
|
675 |
|
675 |
|
676 |
|
676 |
|
|
677 |
|
|
|
678 |
|
|
|
679 |
|
|
|
680 |
|
|
|
681 |
|
|
677 |
|
682 |
|
678 |
|
683 |
|
679 |
|
684 |
|
|
|
||
732 |
|
737 |
|
733 |
|
738 |
|
734 |
|
739 |
|
|
740 |
|
|
735 |
|
741 |
|
736 |
|
742 |
|
737 |
|
743 |
|
738 |
|
744 |
|
739 |
|
745 |
|
740 |
|
746 |
|
741 |
|
|
|
|
747 |
|
|
742 |
|
748 |
|
743 |
|
749 |
|
744 |
|
750 |
|