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: Hayato Kiwata <dev@haytok.jp>, passt-dev@passt.top
Subject: Re: [PATCH] fwd, conf: Roll back to old rules if switching to new ones fails
Date: Wed, 11 Nov 2026 19:57:48 +1100	[thread overview]
Message-ID: <avQt_1gH8c_M1Pt9@gractus.seuss> (raw)
In-Reply-To: <20261111080326.32637ece@elisabeth>

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

On Wed, Nov 11, 2026 at 08:03:26AM +0100, Stefano Brivio wrote:
> On Fri, 30 Oct 2026 01:28:58 +0900
> Hayato Kiwata <dev@haytok.jp> wrote:
> 
> > If fwd_listen_init() fails while switching to new forwarding rules
> > received from pesto, we currently close the old listening sockets,
> > report an error and keep the (partially bound) new rules. That leaves
> > pasta in a state the user didn't ask for.
> > 
> > Make fwd_listen_switch() return the result of fwd_listen_init(), and
> > call it a second time from conf_handler() on failure to switch back
> > to the old rules.
> 
> Ah, right, brilliant!  I didn't realise that it doesn't actually need
> any further change because the other rules are always in
> c->fwd_pending.

Right, I made it that way on purpose to support this kind of revert.

-- 
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-11-11  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 16:28 Hayato Kiwata
2026-11-11  7:03 ` Stefano Brivio
2026-11-11  8:57   ` 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=avQt_1gH8c_M1Pt9@gractus.seuss \
    --to=david@gibson.dropbear.id.au \
    --cc=dev@haytok.jp \
    --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).