public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v3 0/3] More graceful handling of migration without passt-repair
Date: Wed, 26 Feb 2025 20:01:13 +0100	[thread overview]
Message-ID: <20250226200113.6f90e066@elisabeth> (raw)
In-Reply-To: <20250226060422.48295-1-david@gibson.dropbear.id.au>

On Wed, 26 Feb 2025 17:04:19 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> From Red Hat internal testing we've had some reports that if
> attempting to migrate without passt-repair, the failure mode is uglier
> than we'd like.  The migration fails, which is somewhat expected, but
> we don't correctly roll things back on the source, so it breaks
> network there as well.
> 
> Handle this more gracefully allowing the migration to proceed in this
> case, but allow TCP connections to break
> 
> I've test patches 1..2/3 reasonably:
>  * I get a clean migration if there are now active flows
>  * Migration completes, although connections are broken if
>    passt-repair isn't connected
>  * Basic test suite (minus perf)
> 
> Patch 3 I've run the basic test suite on, but haven't tested the
> specific functionality of.  Alas, I've spent most of today battling
> with RHEL, virt-install, unshare and various other things trying to
> create a test environment simulating two hosts with (possibly)
> different addresses.

Sorry, I've been busy with other stuff most of the day and I didn't
manage to test the specific functionality of 3/3 either. :(

I reviewed this and it all looks good to me but I'm not sure if I
should merge this now or wait until we manage to test the 3/3 case. Let
me know your preference. I can also merge up to 2/3 if it makes things
more convenient.

-- 
Stefano


  parent reply	other threads:[~2025-02-26 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26  6:04 [PATCH v3 0/3] More graceful handling of migration without passt-repair David Gibson
2025-02-26  6:04 ` [PATCH v3 1/3] migrate, flow: Trivially succeed if migrating with no flows David Gibson
2025-02-26  6:04 ` [PATCH v3 2/3] migrate, flow: Don't attempt to migrate TCP flows without passt-repair David Gibson
2025-02-26  6:04 ` [PATCH v3 3/3] migrate, tcp: Don't attempt to carry on migration after flow_alloc_cancel() David Gibson
2025-02-26 19:01 ` Stefano Brivio [this message]
2025-02-27  1:23   ` [PATCH v3 0/3] More graceful handling of migration without passt-repair David Gibson

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=20250226200113.6f90e066@elisabeth \
    --to=sbrivio@redhat.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).