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 02/18] conf: Simplify handling of default forwarding mode
Date: Wed, 08 Apr 2026 01:14:36 +0200 (CEST)	[thread overview]
Message-ID: <20260408011435.3b425877@elisabeth> (raw)
In-Reply-To: <20260407031630.2457081-3-david@gibson.dropbear.id.au>

On Tue,  7 Apr 2026 13:16:14 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> For passt, the default forwarding mode is "none", which falls out naturally
> from the other handling: if we don't get any options, we get empty
> forwarding tables, which corresponds to "none" behaviour.  However, for
> pasta the default is "auto".  This is handled a bit oddly: in conf_ports()
> we set the mode variable, but don't set up the rules we need for "auto"
> mode.  Instead we want until nearly the end of conf() and if the mode is
> FWD_MODE_AUTO or unset, we make conf_ports_range_except() calls to set up
> the "auto" rules.
> 
> Simplify this a bit, by creating the rules within conf_ports() itself when
> we parse -[tuTU] auto.  For the case of no forwarding options we call
> into conf_ports() itself with synthetic arguments.  As well as making the
> code a little shorter, this makes it more obvious that giving no arguments
> really is equivalent to -[tuTU] auto.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
>  conf.c | 54 ++++++++++++++++++++++--------------------------------
>  1 file changed, 22 insertions(+), 32 deletions(-)
> 
> diff --git a/conf.c b/conf.c
> index c515480b..7d718f91 100644
> --- a/conf.c
> +++ b/conf.c
> @@ -345,6 +345,10 @@ static void conf_ports(const struct ctx *c, char optname, const char *optarg,
>  			die("'auto' port forwarding is only allowed for pasta");
>  
>  		*mode = FWD_MODE_AUTO;
> +
> +		conf_ports_range_except(c, optname, optarg, fwd, NULL, NULL,
> +					1, NUM_PORTS - 1, NULL, 1, FWD_SCAN);
> +
>  		return;
>  	}

Pre-existing, it goes away in 12/18 of the current series, and it's
harmless unless somebody should ever touch 'enum fwd_mode' in a rather
unlikely way: the code here checks:

		if (*mode)
			...

relying on the fact that FWD_MODE_UNSPEC is 0 (and we also have a _NONE
value, which makes it somewhat risky) instead of directly checking if
(*mode == FWD_MODE_UNSPEC).

I thought I would note it here in the unlikely case we'd need to back to
mode constants for whatever reason.

-- 
Stefano


  reply	other threads:[~2026-04-07 23:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07  3:16 [PATCH 00/18] Rework forwarding option parsing David Gibson
2026-04-07  3:16 ` [PATCH 01/18] conf: Split parsing of port specifiers from the rest of -[tuTU] parsing David Gibson
2026-04-07  3:16 ` [PATCH 02/18] conf: Simplify handling of default forwarding mode David Gibson
2026-04-07 23:14   ` Stefano Brivio [this message]
2026-04-08  1:10     ` David Gibson
2026-04-07  3:16 ` [PATCH 03/18] conf: Move first pass handling of -[TU] next to handling of -[tu] David Gibson
2026-04-07  3:16 ` [PATCH 04/18] doc: Consolidate -[tu] option descriptions for passt and pasta David Gibson
2026-04-07 23:14   ` Stefano Brivio
2026-04-08  1:23     ` David Gibson
2026-04-07  3:16 ` [PATCH 05/18] conf: Permit -[tTuU] all in pasta mode David Gibson
2026-04-07  3:16 ` [PATCH 06/18] fwd: Better split forwarding rule specification from associated sockets David Gibson
2026-04-07 23:14   ` Stefano Brivio
2026-04-08  1:30     ` David Gibson
2026-04-08 21:39       ` Stefano Brivio
2026-04-09  0:47         ` David Gibson
2026-04-07  3:16 ` [PATCH 07/18] fwd_rule: Move forwarding rule formatting David Gibson
2026-04-07  3:16 ` [PATCH 08/18] conf: Pass protocol explicitly to conf_ports_range_except() David Gibson
2026-04-07  3:16 ` [PATCH 09/18] fwd: Split rule building from rule adding David Gibson
2026-04-07  3:16 ` [PATCH 10/18] fwd_rule: Move rule conflict checking from fwd_rule_add() to caller David Gibson
2026-04-07 23:14   ` Stefano Brivio
2026-04-08  1:37     ` David Gibson
2026-04-08  4:42       ` David Gibson
2026-04-07  3:16 ` [PATCH 11/18] fwd: Improve error handling in fwd_rule_add() David Gibson
2026-04-08 21:40   ` Stefano Brivio
2026-04-09  0:10     ` David Gibson
2026-04-07  3:16 ` [PATCH 12/18] conf: Don't be strict about exclusivity of forwarding mode David Gibson
2026-04-08 21:40   ` Stefano Brivio
2026-04-09  0:12     ` David Gibson
2026-04-07  3:16 ` [PATCH 13/18] conf: Rework stepping through chunks of port specifiers David Gibson
2026-04-08 21:40   ` Stefano Brivio
2026-04-09  0:13     ` David Gibson
2026-04-07  3:16 ` [PATCH 14/18] conf: Rework checking for garbage after a range David Gibson
2026-04-08 21:40   ` Stefano Brivio
2026-04-09  0:15     ` David Gibson
2026-04-07  3:16 ` [PATCH 15/18] conf: Move "all" handling to port specifier David Gibson
2026-04-08 21:40   ` Stefano Brivio
2026-04-07  3:16 ` [PATCH 16/18] conf: Allow user-specified auto-scanned port forwarding ranges David Gibson
2026-04-08 21:40   ` Stefano Brivio
2026-04-07  3:16 ` [PATCH 17/18] conf: Move SO_BINDTODEVICE workaround to conf_ports() David Gibson
2026-04-07  3:16 ` [PATCH 18/18] conf: Don't pass raw commandline argument to conf_ports_spec() 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=20260408011435.3b425877@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).