net: tcp: Use correct seqnum for tcp_out and tcp_out_ext #90636
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on TCP Spec., the outgoing TCP packets shoud use SND.NXT as the seqnum. In Zephyr, the conn->seq works as the SND.UNA and the conn->seq + conn->unacked_len works as the SND.NXT. Currently, it uses SND.UNA in tcp_out() as the seqnum, which might get dropped as old packets and could not deliver the message to the peer. A few exceptions use SND.NXT - 1 as the seqnum are: keepalive, zero-window-probe, FIN/SYN retransmissions.
And, for closing a connection, Zephyr won't send out FIN until all the data has been ACKed, so the conn->unacked_len is 0 and it is ok to use conn->seq as the SND.NXT.