netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [iptables PATCH] nft: Exit if nftnl_alloc_expr fails
Date: Wed, 15 Jun 2022 09:04:00 +0200	[thread overview]
Message-ID: <YqmEYNjjLO5WKgfr@salvia> (raw)
In-Reply-To: <20220614164457.4592-1-phil@nwl.cc>

On Tue, Jun 14, 2022 at 06:44:57PM +0200, Phil Sutter wrote:
> In some code-paths, 'reg' pointer remaining unallocated is used later so
> at least minimal error checking is necessary. Given that a call to
> nftnl_alloc_expr() should never fail with sane argument, complain and
> exit if it happens.
> 
> Fixes: 7e38890c6b4fb ("nft: prepare for dynamic register allocation")
> Signed-off-by: Phil Sutter <phil@nwl.cc>
> ---
>  iptables/nft-shared.c | 32 +++++++++++++++++---------------
>  1 file changed, 17 insertions(+), 15 deletions(-)
> 
> diff --git a/iptables/nft-shared.c b/iptables/nft-shared.c
> index 27e95c1ae4f38..d603e7c9d663b 100644
> --- a/iptables/nft-shared.c
> +++ b/iptables/nft-shared.c
> @@ -40,15 +40,25 @@ extern struct nft_family_ops nft_family_ops_ipv6;
>  extern struct nft_family_ops nft_family_ops_arp;
>  extern struct nft_family_ops nft_family_ops_bridge;
>  
> +static struct nftnl_expr *nftnl_expr_alloc_or_die(const char *name)

better call this:

xt_nftnl_expr_alloc()

or such, to not enter nftnl_ namespace, I'd suggest.

> +{
> +	struct nftnl_expr *expr = nftnl_expr_alloc(name);
> +
> +	if (expr)
> +		return expr;
> +

extra line space.

> +
> +	xtables_error(RESOURCE_PROBLEM,
> +		      "Failed to allocate nftnl expression '%s'", name);
> +}
> +
>  void add_meta(struct nft_handle *h, struct nftnl_rule *r, uint32_t key,
>  	      uint8_t *dreg)
>  {
>  	struct nftnl_expr *expr;
>  	uint8_t reg;
>  
> -	expr = nftnl_expr_alloc("meta");
> -	if (expr == NULL)
> -		return;
> +	expr = nftnl_expr_alloc_or_die("meta");
>  
>  	reg = NFT_REG_1;
>  	nftnl_expr_set_u32(expr, NFTNL_EXPR_META_KEY, key);
> @@ -64,9 +74,7 @@ void add_payload(struct nft_handle *h, struct nftnl_rule *r,
>  	struct nftnl_expr *expr;
>  	uint8_t reg;
>  
> -	expr = nftnl_expr_alloc("payload");
> -	if (expr == NULL)
> -		return;
> +	expr = nftnl_expr_alloc_or_die("payload");
>  
>  	reg = NFT_REG_1;
>  	nftnl_expr_set_u32(expr, NFTNL_EXPR_PAYLOAD_BASE, base);
> @@ -85,9 +93,7 @@ void add_bitwise_u16(struct nft_handle *h, struct nftnl_rule *r,
>  	struct nftnl_expr *expr;
>  	uint8_t reg;
>  
> -	expr = nftnl_expr_alloc("bitwise");
> -	if (expr == NULL)
> -		return;
> +	expr = nftnl_expr_alloc_or_die("bitwise");
>  
>  	reg = NFT_REG_1;
>  	nftnl_expr_set_u32(expr, NFTNL_EXPR_BITWISE_SREG, sreg);
> @@ -107,9 +113,7 @@ void add_bitwise(struct nft_handle *h, struct nftnl_rule *r,
>  	uint32_t xor[4] = { 0 };
>  	uint8_t reg = *dreg;
>  
> -	expr = nftnl_expr_alloc("bitwise");
> -	if (expr == NULL)
> -		return;
> +	expr = nftnl_expr_alloc_or_die("bitwise");
>  
>  	nftnl_expr_set_u32(expr, NFTNL_EXPR_BITWISE_SREG, sreg);
>  	nftnl_expr_set_u32(expr, NFTNL_EXPR_BITWISE_DREG, reg);
> @@ -126,9 +130,7 @@ void add_cmp_ptr(struct nftnl_rule *r, uint32_t op, void *data, size_t len,
>  {
>  	struct nftnl_expr *expr;
>  
> -	expr = nftnl_expr_alloc("cmp");
> -	if (expr == NULL)
> -		return;
> +	expr = nftnl_expr_alloc_or_die("cmp");
>  
>  	nftnl_expr_set_u32(expr, NFTNL_EXPR_CMP_SREG, sreg);
>  	nftnl_expr_set_u32(expr, NFTNL_EXPR_CMP_OP, op);
> -- 
> 2.34.1
> 

  reply	other threads:[~2022-06-15  7:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 16:44 [iptables PATCH] nft: Exit if nftnl_alloc_expr fails Phil Sutter
2022-06-15  7:04 ` Pablo Neira Ayuso [this message]
2022-06-15  8:47   ` Phil Sutter

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=YqmEYNjjLO5WKgfr@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=phil@nwl.cc \
    /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.
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 NNTP newsgroup(s).