From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
passt-dev@passt.top, Jon Maloy <jmaloy@redhat.com>
Subject: Re: [PATCH v7 17/18] conf, fwd: Allow switching to new rules received from pesto
Date: Wed, 6 May 2026 00:32:16 +1000 [thread overview]
Message-ID: <afn_cAPUeoMTXxRp@zatzit> (raw)
In-Reply-To: <20260505120408.6f14cc15@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 5375 bytes --]
On Tue, May 05, 2026 at 12:04:09PM +0200, Stefano Brivio wrote:
> On Tue, 5 May 2026 11:08:27 +0200
> Laurent Vivier <lvivier@redhat.com> wrote:
>
> > On 5/5/26 01:11, Stefano Brivio wrote:
> > > From: David Gibson <david@gibson.dropbear.id.au>
> > >
> > > We can now receive updates to the forwarding rules from the pesto client
> > > and store them in a "pending" copy of the forwarding tables. Implement
> > > switching to using the new rules.
> > >
> > > The logic is in a new fwd_listen_switch(). For now this closes all
> > > listening sockets related to the old tables, swaps the active and pending
> > > tables, then listens based on the new tables. In future we look to improve
> > > this so that we don't temporarily stop listening on ports that both the
> > > old and new tables specify.
> > >
> > > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> > > ---
> > > conf.c | 5 ++---
> > > fwd.c | 34 ++++++++++++++++++++++++++++++++++
> > > fwd.h | 1 +
> > > 3 files changed, 37 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/conf.c b/conf.c
> > > index f035fd3..75b8291 100644
> > > --- a/conf.c
> > > +++ b/conf.c
> > > @@ -2159,15 +2159,14 @@ void conf_handler(struct ctx *c, uint32_t events)
> > > fwd_rules_dump(info, fwd->rules, fwd->count,
> > > " ", "");
> > > }
> > > +
> > > + fwd_listen_switch(c);
> > > }
> > >
> > > if (events & EPOLLHUP) {
> > > debug("Configuration client hangup");
> > > - goto close;
> > > }
> > >
> > > - return;
> > > -
> > > close:
> > > conf_close(c);
> > >
> > > diff --git a/fwd.c b/fwd.c
> > > index d93d2e5..35b9e2b 100644
> > > --- a/fwd.c
> > > +++ b/fwd.c
> > > @@ -534,6 +534,40 @@ int fwd_listen_init(const struct ctx *c)
> > > return 0;
> > > }
> > >
> > > +/**
> > > + * fwd_listen_switch() - Switch from current to pending rules table
> > > + * @c: Execution context
> > > + */
> > > +void fwd_listen_switch(struct ctx *c)
> > > +{
> > > + struct fwd_table *tmp[PIF_NUM_TYPES];
> > > + unsigned i;
> > > +
> > > + /* Stop listening on the old tables */
> > > + for (i = 0; i < PIF_NUM_TYPES; i++) {
> > > + struct fwd_table *fwd = c->fwd[i];
> > > +
> > > + if (!fwd)
> > > + continue;
> > > +
> > > + debug("Flushing %u old %s rules", fwd->count, pif_name(i));
> > > + fwd_listen_close(fwd);
> > > + fwd->count = fwd->sock_count = 0;
> >
> > Perhaps we can reset fwd->count and fwd->sock_count in fwd_listen_close() as after
> > fwd_listen_close() these values are wrong?
>
> Right, while not strictly necessary it still looks like a good idea,
> I'll change that.
As noted elswhere this is correct as it is.
> > > + }
> > > +
> > > + /* Swap active and pending tables */
> > > + static_assert(sizeof(tmp) == sizeof(c->fwd) &&
> > > + sizeof(tmp) == sizeof(c->fwd_pending),
> > > + "Temporary has wrong size");
> > > + memcpy(&tmp, (void *)c->fwd, sizeof(tmp));
> > > + memcpy((void *)c->fwd, (void *)c->fwd_pending, sizeof(tmp));
> > > + memcpy((void *)c->fwd_pending, &tmp, sizeof(tmp));
> >
> > I know we have the static_assert(), but with memcpy() we usually use the sizeof() of the
> > destination to avoid write overflow.
>
> I'll change this as well.
Sounds good.
> > Why do we keep the old active table? Do we plan to have a "--restore" option?
>
> It's just to add and delete rules using a temporary table so that we
> can abort cleanly and atomically on errors.
>
> Are you asking why we don't wipe the old table afterwards? No
> particular reason for that, even though I'm not sure if it's useful.
Also looking ahead to listening socket continuity. In that case we
need to keep the old table until we've stolen all the sockets we can
re-use for the new table. *Then* we can fwd_listen_close() anything
left over, and wipe the table.
> Actually some kind of --restore option might be desirable, even though
> we would probably need to re-validate all the rules, or keep a "dirty"
> bit that's set on other types of changes and would tell us that the
> previous table can't be used as it is anymore.
>
> --
> Stefano
>
>
> > > +
> > > + /* Start listening on the new tables */
> > > + if (fwd_listen_init(c) < 0)
> > > + err("Error switching to new forwarding rules");
> > > +}
> > > +
> > > /* See enum in kernel's include/net/tcp_states.h */
> > > #define UDP_LISTEN 0x07
> > > #define TCP_LISTEN 0x0a
> > > diff --git a/fwd.h b/fwd.h
> > > index ac24782..b60697d 100644
> > > --- a/fwd.h
> > > +++ b/fwd.h
> > > @@ -61,6 +61,7 @@ int fwd_listen_sync(const struct ctx *c, uint8_t pif,
> > > const struct fwd_scan *tcp, const struct fwd_scan *udp);
> > > void fwd_listen_close(const struct fwd_table *fwd);
> > > int fwd_listen_init(const struct ctx *c);
> > > +void fwd_listen_switch(struct ctx *c);
> > >
> > > bool nat_inbound(const struct ctx *c, const union inany_addr *addr,
> > > union inany_addr *translated);
> >
>
--
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 --]
next prev parent reply other threads:[~2026-05-05 14:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 23:11 [PATCH v7 00/18] Dynamic configuration update implementation Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 01/18] conf, fwd: Stricter rule checking in fwd_rule_add() Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 02/18] fwd_rule: Move ephemeral port probing to fwd_rule.c Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 03/18] fwd, conf: Move rule parsing code to fwd_rule.[ch] Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 04/18] fwd_rule: Move conflict checking back within fwd_rule_add() Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 05/18] fwd: Generalise fwd_rules_info() Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 06/18] pif: Limit pif names to 128 bytes Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 07/18] fwd_rule: Fix some format specifiers Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 08/18] pesto: Introduce stub configuration tool Stefano Brivio
2026-05-05 7:06 ` Laurent Vivier
2026-05-04 23:11 ` [PATCH v7 09/18] pesto, log: Share log.h (but not log.c) with pesto tool Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 10/18] pesto, conf: Have pesto connect to passt and check versions Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 11/18] pesto: Expose list of pifs to pesto and display them Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 12/18] ip: Prepare ip.[ch] for sharing with pesto tool Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 13/18] inany: Prepare inany.[ch] " Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 14/18] pesto: Read current ruleset from passt/pasta and optionally display it Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 15/18] pesto: Parse and add new rules from command line Stefano Brivio
2026-05-05 7:31 ` Laurent Vivier
2026-05-05 23:47 ` Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 16/18] pesto, conf: Send updated rules from pesto back to passt/pasta Stefano Brivio
2026-05-05 7:53 ` Laurent Vivier
2026-05-05 9:58 ` David Gibson
2026-05-05 10:04 ` Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 17/18] conf, fwd: Allow switching to new rules received from pesto Stefano Brivio
2026-05-05 9:08 ` Laurent Vivier
2026-05-05 9:53 ` David Gibson
2026-05-05 10:15 ` Stefano Brivio
2026-05-05 10:20 ` Laurent Vivier
2026-05-05 14:29 ` David Gibson
2026-05-05 10:04 ` Stefano Brivio
2026-05-05 14:32 ` David Gibson [this message]
2026-05-05 23:47 ` Stefano Brivio
2026-05-04 23:11 ` [PATCH v7 18/18] fwd_rule: Fix static checkers warnings in fwd_rule_add() Stefano Brivio
2026-05-05 6:22 ` David Gibson
2026-05-05 10:13 ` Stefano Brivio
2026-05-05 14:41 ` David Gibson
2026-05-06 7:46 ` Stefano Brivio
2026-05-06 8:00 ` David Gibson
2026-05-06 8:25 ` Stefano Brivio
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=afn_cAPUeoMTXxRp@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--cc=lvivier@redhat.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).