aboutgitcodebugslistschat
path: root/test/tcp
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2026-01-30 15:41:02 +1100
committerStefano Brivio <sbrivio@redhat.com>2026-01-31 03:56:50 +0100
commite992b14b405ec4d0f4ea40b447029e23cbc2e30d (patch)
tree224557605c175eed73aadf29bb0d58c4d44be19f /test/tcp
parente3f70c05bad90368a1a89bf31a9015125232b9ae (diff)
downloadpasst-e992b14b405ec4d0f4ea40b447029e23cbc2e30d.tar
passt-e992b14b405ec4d0f4ea40b447029e23cbc2e30d.tar.gz
passt-e992b14b405ec4d0f4ea40b447029e23cbc2e30d.tar.bz2
passt-e992b14b405ec4d0f4ea40b447029e23cbc2e30d.tar.lz
passt-e992b14b405ec4d0f4ea40b447029e23cbc2e30d.tar.xz
passt-e992b14b405ec4d0f4ea40b447029e23cbc2e30d.tar.zst
passt-e992b14b405ec4d0f4ea40b447029e23cbc2e30d.zip
tcp: Retransmit FINs like data segments
RFC 9293 doesn't distinguish between regular data segments and FIN segments for the purposes of retransmissions. Our existing retransmission logic will also work for FIN segments, except for one detail: we don't currently set the ACK_FROM_TAP_DUE flag when we send a FIN. Add the flag, so that we'll properly retransmit FIN segments like data segments. Remove the section from the theory of operation comment that describes a different way of handling FIN timeouts which (a) isn't correct behaviour and (b) doesn't appear to be implemented. I've tested this by adding logic to suppress sending the FIN if retries < some non-zero value. We correctly resend the FIN and close normally after the expected timeouts. Link: https://bugs.passt.top/show_bug.cgi?id=195 Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test/tcp')
0 files changed, 0 insertions, 0 deletions