From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft 1/2] evaluate: prepare to store expr key rather than datatype
Date: Wed, 27 Sep 2017 14:19:51 +0200 [thread overview]
Message-ID: <20170927121951.GA26052@salvia> (raw)
In-Reply-To: <20170919124954.26852-2-fw@strlen.de>
On Tue, Sep 19, 2017 at 02:49:53PM +0200, Florian Westphal wrote:
> currently set definitions store a datatype rather than
> an expression.
>
> In order to support use of unqualified data types (string in particular),
> this prepares implicit set definition helper to expect an expression instead
> of plain data type. This also has the advantage that we can use EXPR_CONCAT
> to retain the original expressions when key concatentation is used, e.g.
> 'meta iifname . tcp dport'. The netlink serialization code can use
> this info to store individual key lengths independently of data types.
>
> Would also allow later on to store the original names of the
> expressions, e.g. "ip daddr", in the kernel to support a future
> typeof keyword, e.g. 'type typeof(ip daddr)' instead of 'type ipv4_addr'.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
next prev parent reply other threads:[~2017-09-27 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 12:49 [PATCH nft 0/2] store expression instead of data type as set key Florian Westphal
2017-09-19 12:49 ` [PATCH nft 1/2] evaluate: prepare to store expr key rather than datatype Florian Westphal
2017-09-27 12:19 ` Pablo Neira Ayuso [this message]
2017-09-19 12:49 ` [PATCH nft 2/2] src: store expression as set key instead of data type Florian Westphal
2017-09-27 12:58 ` Pablo Neira Ayuso
2017-09-27 13:02 ` Florian Westphal
2017-09-27 13:12 ` Florian Westphal
2017-09-27 13:59 ` Pablo Neira Ayuso
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=20170927121951.GA26052@salvia \
--to=pablo@netfilter.org \
--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).