From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v3 21/25] pesto: Read current ruleset from passt/pasta and display it
Date: Wed, 25 Mar 2026 01:56:39 +0100 (CET) [thread overview]
Message-ID: <20260325015638.0760a30d@elisabeth> (raw)
In-Reply-To: <20260323073732.3158468-22-david@gibson.dropbear.id.au>
On Mon, 23 Mar 2026 18:37:28 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> Implement serialisation of our current forwarding rules in conf.c,
> deserialising it to display in the pesto client.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> conf.c | 44 +++++++++++++++++++++++++++++++
> fwd_rule.c | 40 ++++++++++++++++++++++++++++
> fwd_rule.h | 3 +++
> pesto.c | 77 +++++++++++++++++++++++++++++++++++++++++++++++++++---
> 4 files changed, 160 insertions(+), 4 deletions(-)
>
> diff --git a/conf.c b/conf.c
> index b878db94..7f311914 100644
> --- a/conf.c
> +++ b/conf.c
> @@ -2338,6 +2338,47 @@ static int conf_send_pifs(const struct ctx *c, int fd)
> return 0;
> }
>
> +/**
> + * conf_send_rules() - Send current forwarding rules to dynamic update client (pesto)
What about:
* conf_send_rules() - Send forwarding rules to configuration client (pesto)
?
> + * @c: Execution context
> + * @fd: Socket to the client
> + *
> + * Return: 0 on success, -1 on failure
> + */
> +static int conf_send_rules(const struct ctx *c, int fd)
> +{
> + unsigned pif;
> +
> + for (pif = 0; pif < PIF_NUM_TYPES; pif++) {
> + const struct fwd_table *fwd = c->fwd[pif];
> + unsigned i;
> +
> + if (!fwd)
> + continue;
> +
> + assert(pif);
> +
> + /* PIF id */
> + if (write_u8(fd, pif))
> + return -1;
> +
> + /* Number of rules */
> + if (write_u32(fd, fwd->count))
> + return -1;
> +
> + for (i = 0; i < fwd->count; i++) {
> + if (fwd_rule_write(fd, &fwd->rules[i].rule))
> + return -1;
> + }
> + }
> +
> + /* Write 0 PIF id to finish */
> + if (write_u8(fd, 0))
We have PIF_NONE, shouldn't we use that to make it obvious that it's an
invalid value?
> + return -1;
> +
> + return 0;
> +}
>
> [...]
I stopped reviewing here, the next patches in my series are anyway mine
and after those I guess it doesn't make sense, yet, that I review in
fine detail, as we'll probably need to change a bunch of things.
--
Stefano
next prev parent reply other threads:[~2026-03-25 0:56 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 7:37 [PATCH v3 00/25] RFC: Read-only dynamic update implementation David Gibson
2026-03-23 7:37 ` [PATCH v3 01/25] conf: runas can be const David Gibson
2026-03-23 7:37 ` [PATCH v3 02/25] vhost_user: Fix assorted minor cppcheck warnings David Gibson
2026-03-23 7:37 ` [PATCH v3 03/25] serialise: Split functions user for serialisation from util.c David Gibson
2026-03-25 0:54 ` Stefano Brivio
2026-03-25 1:50 ` David Gibson
2026-03-23 7:37 ` [PATCH v3 04/25] serialise: Add helpers for serialising unsigned integers David Gibson
2026-03-23 7:37 ` [PATCH v3 05/25] fwd: Move selecting correct scan bitmap into fwd_sync_one() David Gibson
2026-03-23 7:37 ` [PATCH v3 06/25] fwd: Look up rule index in fwd_sync_one() David Gibson
2026-03-23 7:37 ` [PATCH v3 07/25] fwd: Store forwarding tables indexed by (origin) pif David Gibson
2026-03-25 0:54 ` Stefano Brivio
2026-03-25 4:04 ` David Gibson
2026-03-23 7:37 ` [PATCH v3 08/25] fwd: Allow FWD_DUAL_STACK_ANY flag to be passed directly to fwd_rule_add() David Gibson
2026-03-25 0:54 ` Stefano Brivio
2026-03-25 4:07 ` David Gibson
2026-03-23 7:37 ` [PATCH v3 09/25] fwd, conf: Expose ephemeral ports as bitmap rather than function David Gibson
2026-03-23 7:37 ` [PATCH v3 10/25] conf: Don't bother complaining about overlapping excluded ranges David Gibson
2026-03-23 7:37 ` [PATCH v3 11/25] conf: Move check for mapping port 0 to caller David Gibson
2026-03-23 7:37 ` [PATCH v3 12/25] conf: Move check for disabled interfaces earlier David Gibson
2026-03-23 7:37 ` [PATCH v3 13/25] pesto: Introduce stub configuration interface and tool David Gibson
2026-03-25 0:54 ` Stefano Brivio
2026-03-23 7:37 ` [PATCH v3 14/25] pesto: Add command line option parsing and debug messages David Gibson
2026-03-25 0:55 ` Stefano Brivio
2026-03-25 4:27 ` David Gibson
2026-03-23 7:37 ` [PATCH v3 15/25] pesto: Expose list of pifs to pesto David Gibson
2026-03-25 0:56 ` Stefano Brivio
2026-03-25 4:34 ` David Gibson
2026-03-25 8:18 ` Stefano Brivio
2026-03-25 8:31 ` David Gibson
2026-03-23 7:37 ` [PATCH v3 16/25] ip: Prepare ip.[ch] for sharing with pesto tool David Gibson
2026-03-23 7:37 ` [PATCH v3 17/25] inany: Prepare inany.[ch] " David Gibson
2026-03-23 7:37 ` [PATCH v3 18/25] fwd: Split forwading rule specification from its implementation state David Gibson
2026-03-23 7:37 ` [PATCH v3 19/25] ip: Define a bound for the string returned by ipproto_name() David Gibson
2026-03-23 7:37 ` [PATCH v3 20/25] fwd_rule: Move forwarding rule text formatting to common code David Gibson
2026-03-25 0:56 ` Stefano Brivio
2026-03-25 4:42 ` David Gibson
2026-03-25 8:18 ` Stefano Brivio
2026-03-25 23:54 ` David Gibson
2026-03-23 7:37 ` [PATCH v3 21/25] pesto: Read current ruleset from passt/pasta and display it David Gibson
2026-03-25 0:56 ` Stefano Brivio [this message]
2026-03-25 4:43 ` David Gibson
2026-03-23 7:37 ` [PATCH v3 22/25] conf: Move port parsing functions to own file, ports.c David Gibson
2026-03-23 7:37 ` [PATCH v3 23/25] conf, fwd, ports, util: Move things around for pesto David Gibson
2026-03-23 7:37 ` [PATCH v3 24/25] pesto, conf: Parse, send and receive new rules David Gibson
2026-03-23 7:37 ` [PATCH v3 25/25] conf, fwd: Allow switching to new rules received from pesto David Gibson
2026-03-23 8:38 ` [PATCH v3 00/25] RFC: Read-only dynamic update implementation David Gibson
2026-03-25 0:56 ` Stefano Brivio
2026-03-25 1:00 ` Stefano Brivio
2026-03-25 4:44 ` 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=20260325015638.0760a30d@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).