public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
	passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Subject: Re: [PATCH v3 05/11] conf: Don't pass raw commandline argument to conf_ports_spec()
Date: Mon, 20 Apr 2026 18:11:12 +0200	[thread overview]
Message-ID: <09fae4b1-415c-4200-8beb-c0975f8891f4@redhat.com> (raw)
In-Reply-To: <20260417050520.102247-6-david@gibson.dropbear.id.au>

On 4/17/26 07:05, David Gibson wrote:
> We only use the optname and optarg parameters for printing error messages,
> and they're not even particularly necessary there.  Remove them.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

Reviewed-by: Laurent Vivier <lvivier@redhat.com>

> ---
>   conf.c | 14 +++++---------
>   1 file changed, 5 insertions(+), 9 deletions(-)
> 
> diff --git a/conf.c b/conf.c
> index 5ff62873..99542075 100644
> --- a/conf.c
> +++ b/conf.c
> @@ -219,8 +219,6 @@ fail:
>   /**
>    * conf_ports_spec() - Parse port range(s) specifier
>    * @c:		Execution context
> - * @optname:	Short option name, t, T, u, or U
> - * @optarg:	Option argument (port specification)
>    * @fwd:	Forwarding table to be updated
>    * @proto:	Protocol to forward
>    * @addr:	Listening address for forwarding
> @@ -228,7 +226,6 @@ fail:
>    * @spec:	Port range(s) specifier
>    */
>   static void conf_ports_spec(const struct ctx *c,
> -			    char optname, const char *optarg,
>   			    struct fwd_table *fwd, uint8_t proto,
>   			    const union inany_addr *addr, const char *ifname,
>   			    const char *spec)
> @@ -316,8 +313,7 @@ static void conf_ports_spec(const struct ctx *c,
>   			goto bad;
>   
>   		if (orig_range.first == 0) {
> -			die("Can't forward port 0 for option '-%c %s'",
> -			    optname, optarg);
> +			die("Can't forward port 0 included in '%s'", spec);
>   		}
>   
>   		conf_ports_range_except(fwd, proto, addr, ifname,
> @@ -328,7 +324,7 @@ static void conf_ports_spec(const struct ctx *c,
>   
>   	return;
>   bad:
> -	die("Invalid port specifier %s", optarg);
> +	die("Invalid port specifier '%s'", spec);
>   }
>   
>   /**
> @@ -432,11 +428,11 @@ static void conf_ports(const struct ctx *c, char optname, const char *optarg,
>   			     optname, optarg);
>   
>   			if (c->ifi4) {
> -				conf_ports_spec(c, optname, optarg, fwd, proto,
> +				conf_ports_spec(c, fwd, proto,
>   						&inany_loopback4, NULL, spec);
>   			}
>   			if (c->ifi6) {
> -				conf_ports_spec(c, optname, optarg, fwd, proto,
> +				conf_ports_spec(c, fwd, proto,
>   						&inany_loopback6, NULL, spec);
>   			}
>   			return;
> @@ -451,7 +447,7 @@ static void conf_ports(const struct ctx *c, char optname, const char *optarg,
>   		    optname, optarg);
>   	}
>   
> -	conf_ports_spec(c, optname, optarg, fwd, proto, addr, ifname, spec);
> +	conf_ports_spec(c, fwd, proto, addr, ifname, spec);
>   }
>   
>   /**


  reply	other threads:[~2026-04-20 16:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  5:05 [PATCH v3 00/11] Rework forwarding option parsing David Gibson
2026-04-17  5:05 ` [PATCH v3 01/11] doc: Rework man page description of port specifiers David Gibson
2026-04-20 13:31   ` Laurent Vivier
2026-04-17  5:05 ` [PATCH v3 02/11] conf: Move "all" handling to port specifier David Gibson
2026-04-20 13:44   ` Laurent Vivier
2026-04-17  5:05 ` [PATCH v3 03/11] conf: Allow user-specified auto-scanned port forwarding ranges David Gibson
2026-04-20 14:45   ` Laurent Vivier
2026-04-17  5:05 ` [PATCH v3 04/11] conf: Move SO_BINDTODEVICE workaround to conf_ports() David Gibson
2026-04-20 15:06   ` Laurent Vivier
2026-04-17  5:05 ` [PATCH v3 05/11] conf: Don't pass raw commandline argument to conf_ports_spec() David Gibson
2026-04-20 16:11   ` Laurent Vivier [this message]
2026-04-17  5:05 ` [PATCH v3 06/11] fwd, conf: Add capabilities bits to each forwarding table David Gibson
2026-04-20 16:17   ` Laurent Vivier
2026-04-17  5:05 ` [PATCH v3 07/11] conf, fwd: Stricter rule checking in fwd_rule_add() David Gibson
2026-04-20 16:48   ` Laurent Vivier
2026-04-17  5:05 ` [PATCH v3 08/11] fwd_rule: Move ephemeral port probing to fwd_rule.c David Gibson
2026-04-20 16:52   ` Laurent Vivier
2026-04-17  5:05 ` [PATCH v3 09/11] fwd, conf: Move rule parsing code to fwd_rule.[ch] David Gibson
2026-04-20 17:06   ` Laurent Vivier
2026-04-17  5:05 ` [PATCH v3 10/11] fwd_rule: Move conflict checking back within fwd_rule_add() David Gibson
2026-04-20 17:15   ` Laurent Vivier
2026-04-17  5:05 ` [PATCH v3 11/11] fwd: Generalise fwd_rules_info() David Gibson
2026-04-20 17:21   ` Laurent Vivier

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=09fae4b1-415c-4200-8beb-c0975f8891f4@redhat.com \
    --to=lvivier@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --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).