public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 0/4] Reworks and improvements to TCP activity timers
Date: Mon, 2 Mar 2026 12:26:13 +1100	[thread overview]
Message-ID: <aaTnNYfPO94EEkpx@zatzit> (raw)
In-Reply-To: <20260225071544.2c4b6de5@elisabeth>

[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]

On Wed, Feb 25, 2026 at 07:15:45AM +0100, Stefano Brivio wrote:
> On Fri,  6 Feb 2026 17:17:35 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > Here's a bunch of patches aimed at fixing bug 179, and reworking the
> > currently broken inactivity timer along the way.
> > 
> > I believe patches 1..2/4 are ready to go - I've tested them, and I'm
> > happy with how they're behaving.  Patches 3..4/4 I think are correct,
> > but I've been getting bogged down in details trying to test them in
> > the specific FIN_WAIT_2 situation that occurs in bug 179.
> 
> I just tested things manually by cycling guest interfaces and checking
> that keepalives come and eventually cause connection resets, as well as
> that the activity timeout (shortened via define) triggers after the
> expected time.

Nice.

> It's not great but I couldn't figure out a way to simulate the issue
> with a single namespace test (without any connecting interface that can
> be brought down), and simulating this with multiple namespaces
> connected via veth looks doable, but not easy to integrate with the
> existing tests.

Right.  I think it can be tested without bouncing interfaces at all -
however it needs quite specific behaviour from both the client and the
server.  I couldn't figure out a way to convince socat to do what I
wanted, so it would probably need custom endpoint programs.

> Meanwhile the reporter of https://bugs.passt.top/show_bug.cgi?id=179
> confirms this series solves the issue, and delaying this further
> doesn't sound like a good idea, so I went ahead and finally applied
> this, fixing a trivial conflict with 812cdb802c6e ("tcp: Move tap
> header update out of tcp_fill_headers()") on the way.

Makes sense to me.

-- 
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 --]

      reply	other threads:[~2026-03-02  1:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06  6:17 David Gibson
2026-02-06  6:17 ` [PATCH v2 1/4] tcp: Remove non-working activity timeout mechanism David Gibson
2026-02-06  6:17 ` [PATCH v2 2/4] tcp: Re-introduce inactivity timeouts based on a clock algorithm David Gibson
2026-02-25  6:15   ` Stefano Brivio
2026-03-02  4:37     ` David Gibson
2026-02-06  6:17 ` [PATCH v2 3/4] tcp: Extend tcp_send_flag() to send TCP keepalive segments David Gibson
2026-02-06  6:17 ` [PATCH v2 4/4] tcp: Send TCP keepalive segments after a period of tap-side inactivity David Gibson
2026-02-25  6:15 ` [PATCH v2 0/4] Reworks and improvements to TCP activity timers Stefano Brivio
2026-03-02  1:26   ` 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=aaTnNYfPO94EEkpx@zatzit \
    --to=david@gibson.dropbear.id.au \
    --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).