From: Phil Sutter <phil@nwl.cc>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH iptables-nft] iptables-nft: must withdraw PAYLOAD flag after parsing
Date: Wed, 21 Sep 2022 18:10:10 +0200 [thread overview]
Message-ID: <Yys3YhGiy7/kegkM@orbyte.nwl.cc> (raw)
In-Reply-To: <20220919213109.GD3498@breakpoint.cc>
On Mon, Sep 19, 2022 at 11:31:09PM +0200, Florian Westphal wrote:
> Florian Westphal <fw@strlen.de> wrote:
> > else, next payload is stacked via 'CTX_PREV_PAYLOAD'.
> >
> > Example breakage:
> >
> > ip saddr 1.2.3.4 meta l4proto tcp
> > ... is dumped as
> > -s 6.0.0.0 -p tcp
> >
> > iptables-nft -s 1.2.3.4 -p tcp is dumped correctly, because
> > the expressions are ordered like:
> > meta l4proto tcp ip saddr 1.2.3.4
> >
> > ... and 'meta l4proto' will clear the PAYLOAD flag.
> >
> > Fixes: 250dce876d92 ("nft-shared: support native tcp port delinearize")
> > Signed-off-by: Florian Westphal <fw@strlen.de>
> > ---
> > iptables/nft-shared.c | 2 ++
> > .../ipt-restore/0018-multi-payload_0 | 27 +++++++++++++++++++
> > 2 files changed, 29 insertions(+)
> > create mode 100755 iptables/tests/shell/testcases/ipt-restore/0018-multi-payload_0
> >
> > diff --git a/iptables/nft-shared.c b/iptables/nft-shared.c
> > index 71e2f18dab92..66e09e8fd533 100644
> > --- a/iptables/nft-shared.c
> > +++ b/iptables/nft-shared.c
> > @@ -986,6 +986,8 @@ static void nft_parse_cmp(struct nft_xt_ctx *ctx, struct nftnl_expr *e)
> > nft_parse_transport(ctx, e, ctx->cs);
> > break;
> > }
> > +
> > + ctx->flags &= ~NFT_XT_CTX_PAYLOAD;
> > }
>
> This isn't ideal either since this breaks dissection of '1-42' ranges
> that use two compare operands, i.e.:
>
> cmp reg1 gte 1
> cmp reg1 lte 42
>
> ...as first cmp 'hides' reg1 again.
>
> I'd propose to rework this context stuff:
> no more payload/meta/whatever flags, instead 'mirror' the raw data
> registers.
>
> Other ideas/suggestions?
When do we use multiple flags? I see we need NFT_XT_CTX_BITWISE in
addition to NFT_XT_CTX_META. Do we need e.g. NFT_XT_CTX_META and
NFT_XT_CTX_PAYLOAD at the same time? My idea would be to use an enum for
the LHS expression which is overwritten by each consecutive LHS
expression and a bitfield for the "on top" stuff.
Cheers, Phil
next prev parent reply other threads:[~2022-09-21 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 20:12 [PATCH iptables-nft] iptables-nft: must withdraw PAYLOAD flag after parsing Florian Westphal
2022-09-19 21:31 ` Florian Westphal
2022-09-21 16:10 ` Phil Sutter [this message]
2022-09-22 14:35 ` Florian Westphal
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=Yys3YhGiy7/kegkM@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.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).