diff options
| author | Stefano Brivio <sbrivio@redhat.com> | 2025-08-29 22:11:26 +0200 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2025-09-11 17:03:21 +0200 |
| commit | 2e3d93ba7033754301af0d50cd0bb20a38a005ac (patch) | |
| tree | 3a6c0058d4a3e475c5cf7a0ae330c78837bf8998 /doc | |
| parent | d363fb7796db3581161a6cca8dd022d0105052dd (diff) | |
| download | passt-2e3d93ba7033754301af0d50cd0bb20a38a005ac.tar passt-2e3d93ba7033754301af0d50cd0bb20a38a005ac.tar.gz passt-2e3d93ba7033754301af0d50cd0bb20a38a005ac.tar.bz2 passt-2e3d93ba7033754301af0d50cd0bb20a38a005ac.tar.lz passt-2e3d93ba7033754301af0d50cd0bb20a38a005ac.tar.xz passt-2e3d93ba7033754301af0d50cd0bb20a38a005ac.tar.zst passt-2e3d93ba7033754301af0d50cd0bb20a38a005ac.zip | |
tcp: FIN flags have to be retransmitted as well
If we're retransmitting any data, and we sent a FIN segment to our
peer, regardless of whether it was received, we obviously have to
retransmit it as well, given that it can only come with the last data
segment, or after it.
Unconditionally clear the internal TAP_FIN_SENT flag whenever we
re-transmit, so that we know we have to send it again, in case.
Reported-by: Paul Holzinger <pholzing@redhat.com>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Tested-by: Paul Holzinger <pholzing@redhat.com>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions