iPXE currently updates the TCP sequence number after delivering the data to the application via xfer_deliver_iob(). If the application responds to the received data by transmitting more data, this would result in a stale ACK number appearing in the transmitted packet, which potentially causes retransmissions and also gives the undesirable appearance of violating causality (by sending a response to a message that we claim not to have yet received). Reported-by: Guo-Fu Tseng <cooldavid@cooldavid.org> Signed-off-by: Michael Brown <mcb30@ipxe.org>tags/v1.20.1
|
|
||
| 702 |
|
702 |
|
| 703 |
|
703 |
|
| 704 |
|
704 |
|
|
705 |
|
|
|
706 |
|
|
|
707 |
|
|
| 705 |
|
708 |
|
| 706 |
|
709 |
|
| 707 |
|
710 |
|
| 708 |
|
711 |
|
| 709 |
|
|
|
| 710 |
|
|
|
| 711 |
|
|
|
| 712 |
|
712 |
|
| 713 |
|
713 |
|
| 714 |
|
714 |
|
|
|
||
| 809 |
|
809 |
|
| 810 |
|
810 |
|
| 811 |
|
811 |
|
|
812 |
|
|
|
813 |
|
|
|
814 |
|
|
| 812 |
|
815 |
|
| 813 |
|
816 |
|
| 814 |
|
817 |
|
|
|
||
| 816 |
|
819 |
|
| 817 |
|
820 |
|
| 818 |
|
821 |
|
| 819 |
|
|
|
| 820 |
|
|
|
| 821 |
|
|
|
| 822 |
|
822 |
|
| 823 |
|
823 |
|
| 824 |
|
824 |
|
|
|
||
| 835 |
|
835 |
|
| 836 |
|
836 |
|
| 837 |
|
837 |
|
| 838 |
|
|
|
| 839 |
|
|
|
|
838 |
|
|
| 840 |
|
839 |
|
| 841 |
|
840 |
|
|
841 |
|
|
|
842 |
|
|
|
843 |
|
|
| 842 |
|
844 |
|
| 843 |
|
845 |
|
| 844 |
|
846 |
|