From: Phil Sutter <phil@nwl.cc>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] parser: move qualified meta expression parsing to flex/bison
Date: Tue, 20 Jan 2026 21:11:54 +0100 [thread overview]
Message-ID: <aW_himZ45y5I1vtf@orbyte.nwl.cc> (raw)
In-Reply-To: <20260120191319.21383-1-fw@strlen.de>
On Tue, Jan 20, 2026 at 08:13:16PM +0100, Florian Westphal wrote:
> The meta keyword currently accepts 'STRING' arguments.
> This was originally done to avoid pollution the global token namespace.
>
> However, nowadays we do have flex scopes to avoid this.
> Add the tokens currently handled implciitly via STRING within
> META flex scope.
>
> SECPATH is a compatibility alias, map this to IPSEC token.
> IBRPORT/OBRPORT are also compatibility aliases, remove those tokens
> and handle this directly in scanner.l.
>
> This also avoids nft from printing tokens in help texts that are only
> there for compatibility with old rulesets.
>
> meta_key_parse() is retained for json input parser.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Acked-by: Phil Sutter <phil@nwl.cc>
prev parent reply other threads:[~2026-01-20 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 19:13 [PATCH nft] parser: move qualified meta expression parsing to flex/bison Florian Westphal
2026-01-20 20:11 ` 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=aW_himZ45y5I1vtf@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