From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [iptables PATCH] nft: Exit if nftnl_alloc_expr fails
Date: Wed, 15 Jun 2022 10:47:59 +0200 [thread overview]
Message-ID: <Yqmcv7LosxwmO9ZR@orbyte.nwl.cc> (raw)
In-Reply-To: <YqmEYNjjLO5WKgfr@salvia>
On Wed, Jun 15, 2022 at 09:04:00AM +0200, Pablo Neira Ayuso wrote:
> 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.
ACK, will do.
> > +{
> > + struct nftnl_expr *expr = nftnl_expr_alloc(name);
> > +
> > + if (expr)
> > + return expr;
> > +
>
> extra line space.
Oh, thanks.
prev parent reply other threads:[~2022-06-15 8:48 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
2022-06-15 8:47 ` Phil Sutter [this message]
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=Yqmcv7LosxwmO9ZR@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).