raiden00pl opened a new pull request, #22137:
URL: https://github.com/apache/nuttx/pull/22137

   ## Summary
   
   `tcp_input()` treats every segment whose sequence number is above RCV.NXT as 
out of order and replies with an ACK, also a segment without data, SYN or FIN. 
When both ends have sent data that the other end dropped, each pure ACK carries 
a sequence number beyond the other end's RCV.NXT, so the two ends answer each 
other's ACKs without end. Over the loopback device the loop never leaves 
`devif_loopback()` and the node stops responding.
   
   RFC 9293, 3.10.7.4: a segment of length 0 is acceptable if RCV.NXT =< 
SEG.SEQ < RCV.NXT+RCV.WND, and only a segment that is not acceptable is 
answered with an ACK. Such a segment now passes a new ACK to the connection and 
is not answered. Segments with data, SYN or FIN, and empty segments beyond the 
window, are handled as before.
   
   ## Impact
   
   TCP input only. No API, ABI or Kconfig change.
   
   ## Testing
   
   - sim: TCP duplex transfers over the node's own address and 127.0.0.1 no 
longer make the node unresponsive.
   - sim: a scripted peer gets no reply to an empty in-window ACK, and gets an 
ACK for an empty segment beyond the window.
   - sim: TCP and IP tests give the same results as master; iperf between two 
nodes is unchanged.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to