public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Aris Konstantoulas <arist.kon@gmail.com>
Cc: passt-dev@passt.top, David Gibson <david@gibson.dropbear.id.au>,
	Aris Konstantoulas <aris@ariscodes.com>
Subject: Re: [PATCH] tcp: Don't fast re-transmit if only our FIN is outstanding
Date: Sat, 03 Oct 2026 00:26:26 +0200 (CEST)	[thread overview]
Message-ID: <20261003002625.3babd1e8@elisabeth> (raw)
In-Reply-To: <20260928103120.233586-1-arist.kon@gmail.com>

On Mon, 28 Sep 2026 13:31:20 +0300
Aris Konstantoulas <arist.kon@gmail.com> wrote:

> From: Aris Konstantoulas <aris@ariscodes.com>
> 
> In the TAP_FIN_RCVD path of tcp_tap_handler(), a bare segment from the
> guest acknowledging exactly seq_ack_from_tap, with an unchanged window,
> is taken as a duplicate ACK and triggers a fast re-transmit.
> 
> If the only unacknowledged sequence number is our own FIN, that's
> harmful: tcp_rewind_seq() rewinds seq_to_tap and clears TAP_FIN_SENT,
> so tcp_data_from_sock() immediately sends the FIN again. If the guest
> answers that FIN with the same bare ACK, as a socket in TIME-WAIT will,
> we loop at packet rate:
> 
> - conn->retries is never incremented on this path, so we never reach
>   TCP_MAX_RETRIES and tcp_rst()
> 
> - ACK_FROM_TAP_DUE is re-armed on every iteration, so the backed-off
>   re-transmission in tcp_timer_handler() never fires
> 
> - TAP_FIN_ACKED can't be set, as it requires TAP_FIN_SENT, which the
>   rewind just cleared
> 
> On an idle Podman host (rootless, pasta), this showed up as a single
> flow exchanging ~45,000 54-byte segments per second between pasta and
> a container whose socket was in TIME-WAIT, with pasta using ~75% of one
> core, until the socket was killed by hand. It recurred on the idle
> teardown of an HTTP/2 connection to an ACME server.
> 
> With a raw-socket peer driving the same sequence against pasta at
> f8df3f1, pasta re-sent the FIN 727,509 times in 10 seconds. With this
> change it's re-transmitted by the timer at 1, 3, 7, 15, 31, 63 and 127
> seconds, and the connection is reset once TCP_MAX_RETRIES is reached.
> 
> Don't consider a duplicate ACK as a fast re-transmit trigger if the
> only outstanding sequence number is the FIN, and leave it to the timer.
> Fast re-transmit of data is unaffected, with or without a FIN queued
> after it.
> 
> Fixes: bde1847960cf ("tcp: Fast re-transmit if half-closed, make TAP_FIN_RCVD path consistent")
> Link: https://bugs.passt.top/show_bug.cgi?id=125
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Aris Konstantoulas <aris@ariscodes.com>
> ---

Applied, thanks for fixing this, and welcome to the git log!

-- 
Stefano


      parent reply	other threads:[~2026-10-02 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 10:31 Aris Konstantoulas
2026-09-29 11:31 ` Stefano Brivio
2026-10-02 22:26 ` Stefano Brivio [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=20261003002625.3babd1e8@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=aris@ariscodes.com \
    --cc=arist.kon@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    /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).