From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: Re: [PATCH] tcp: Flush socket before checking for more data in active close state
Date: Thu, 20 Mar 2025 11:33:51 +1100 [thread overview]
Message-ID: <Z9tib_AOwWNFbU1S@zatzit> (raw)
In-Reply-To: <20250319190519.3184123-1-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2171 bytes --]
On Wed, Mar 19, 2025 at 08:05:19PM +0100, Stefano Brivio wrote:
> Otherwise, if all the pending data is acknowledged:
>
> - tcp_update_seqack_from_tap() updates the current tap-side ACK
> sequence (conn->seq_ack_from_tap)
>
> - next, we compare the sequence we sent (conn->seq_to_tap) to the
> ACK sequence (conn->seq_ack_from_tap) in tcp_data_from_sock() to
> understand if there's more data we can send.
>
> If they match, we conclude that we haven't sent any of that data,
> and keep re-sending it.
>
> We need, instead, to flush the socket (drop acknowledged data) before
> calling tcp_update_seqack_from_tap(), so that once we update
> conn->seq_ack_from_tap, we can be sure that all data until there is
> gone from the socket.
IIUC, this is, roughly speaking, a manifestation of the difference
between "seq ack from tap" and "seq ack to sock". We don't track the
latter, because it's kind of implied by the former. However, with the
incorrect ordering here the brief window in which they're not the same
is biting us.
> Link: https://bugs.passt.top/show_bug.cgi?id=114
> Reported-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> Fixes: 30f1e082c3c0 ("tcp: Keep updating window and checking for socket data after FIN from guest")
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> tcp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tcp.c b/tcp.c
> index 68af43d..fa1d885 100644
> --- a/tcp.c
> +++ b/tcp.c
> @@ -2049,6 +2049,7 @@ int tcp_tap_handler(const struct ctx *c, uint8_t pif, sa_family_t af,
>
> /* Established connections not accepting data from tap */
> if (conn->events & TAP_FIN_RCVD) {
> + tcp_sock_consume(conn, ntohl(th->ack_seq));
> tcp_update_seqack_from_tap(c, conn, ntohl(th->ack_seq));
> tcp_tap_window_update(conn, ntohs(th->window));
> tcp_data_from_sock(c, conn);
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-03-20 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 19:05 [PATCH] tcp: Flush socket before checking for more data in active close state Stefano Brivio
2025-03-20 0:33 ` David Gibson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z9tib_AOwWNFbU1S@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=marmarek@invisiblethingslab.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).