public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Jon Maloy <jmaloy@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>, passt-dev@passt.top
Subject: Re: [PATCH v5 15/18] pesto: Read current ruleset from passt/pasta and optionally display it
Date: Sat, 25 Apr 2026 09:36:05	[thread overview]
Message-ID: <20260425113558.2dbc419e@elisabeth> (raw)
In-Reply-To: <ca2dc7e8-5df7-4db7-9f75-2b3119c027ca@redhat.com>

On Fri, 24 Apr 2026 18:37:58 -0400
Jon Maloy <jmaloy@redhat.com> wrote:

> On 2026-04-21 02:25, David Gibson wrote:
> > Implement serialisation of our current forwarding rules in conf.c,
> > deserialising it to display in the pesto client.  Doing this requires
> > adding ip.c, inany.c, bitmap.c, lineread.c and fwd_rule.c to the pesto
> > build.  With previous preparations that now requires only a trivial change  
> [...]
> 
> > +
> > +
> > +/**
> > + * fwd_rule_read() - Read serialised rule from an fd
> > + * @fd:		fd to serialise to
> > + * @rule:	Buffer to store rule into
> > + *
> > + * Return: 0 on success, -1 on error (with errno set)
> > + */
> > +int fwd_rule_read(int fd, struct fwd_rule *rule)
> > +{
> > +	if (read_all_buf(fd, rule, sizeof(*rule)))
> > +		return -1;
> > +
> > +	/* Byteswap for host */
> > +	rule->first = ntohs(rule->first);
> > +	rule->last = ntohs(rule->last);
> > +	rule->to = htons(rule->to);  
> Or ntohs() ?

Thanks, nice catch, I'll fix this (I'm adopting this series and trying
to complete it while David is off).

-- 
Stefano


  reply	other threads:[~2026-04-25  9:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  6:24 [PATCH v5 00/18] RFC: Dynamic configuration update implementation David Gibson
2026-04-21  6:24 ` [PATCH v5 01/18] conf, fwd: Stricter rule checking in fwd_rule_add() David Gibson
2026-04-25 13:31   ` Jon Maloy
2026-04-27  3:20     ` David Gibson
2026-04-21  6:25 ` [PATCH v5 02/18] fwd_rule: Move ephemeral port probing to fwd_rule.c David Gibson
2026-04-21  6:25 ` [PATCH v5 03/18] fwd, conf: Move rule parsing code to fwd_rule.[ch] David Gibson
2026-04-24 21:59   ` Jon Maloy
2026-04-24 22:36   ` Jon Maloy
2026-04-21  6:25 ` [PATCH v5 04/18] fwd_rule: Move conflict checking back within fwd_rule_add() David Gibson
2026-04-21  6:25 ` [PATCH v5 05/18] fwd: Generalise fwd_rules_info() David Gibson
2026-04-21  6:25 ` [PATCH v5 06/18] pif: Limit pif names to 128 bytes David Gibson
2026-04-21  6:25 ` [PATCH v5 07/18] fwd_rule: Fix some format specifiers David Gibson
2026-04-21  6:25 ` [PATCH v5 08/18] tap, repair: Use SOCK_NONBLOCK and SOCK_CLOEXEC on Unix sockets David Gibson
2026-04-21  6:25 ` [PATCH v5 09/18] pesto: Introduce stub configuration tool David Gibson
2026-04-21  6:25 ` [PATCH v5 10/18] pesto, log: Share log.h (but not log.c) with pesto tool David Gibson
2026-04-21  6:25 ` [PATCH v5 11/18] pesto, conf: Have pesto connect to passt and check versions David Gibson
2026-04-26 13:45   ` Jon Maloy
2026-04-29  5:18     ` David Gibson
2026-04-21  6:25 ` [PATCH v5 12/18] pesto: Expose list of pifs to pesto and optionally display David Gibson
2026-04-26 13:45   ` Jon Maloy
2026-04-29  5:17     ` David Gibson
2026-04-21  6:25 ` [PATCH v5 13/18] ip: Prepare ip.[ch] for sharing with pesto tool David Gibson
2026-04-21  6:25 ` [PATCH v5 14/18] inany: Prepare inany.[ch] " David Gibson
2026-04-21  6:25 ` [PATCH v5 15/18] pesto: Read current ruleset from passt/pasta and optionally display it David Gibson
2026-04-24 22:37   ` Jon Maloy
2026-04-25  7:36     ` Stefano Brivio [this message]
2026-04-29  5:19       ` David Gibson
2026-04-21  6:25 ` [PATCH v5 16/18] pesto: Parse and add new rules from command line David Gibson
2026-04-21  6:25 ` [PATCH v5 17/18] pesto, conf: Send updated rules from pesto back to passt/pasta David Gibson
2026-04-24 22:38   ` Jon Maloy
2026-04-25  7:36     ` Stefano Brivio
2026-04-29  5:21       ` David Gibson
2026-04-21  6:25 ` [PATCH v5 18/18] conf, fwd: Allow switching to new rules received from pesto 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=20260425113558.2dbc419e@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=jmaloy@redhat.com \
    --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).