From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Subject: [PATCH nftables 0/8] add typeof keyword
Date: Fri, 16 Aug 2019 16:42:33 +0200 [thread overview]
Message-ID: <20190816144241.11469-1-fw@strlen.de> (raw)
This patch series adds the typeof keyword.
The only dependency is a small change to libnftnl to add two new
UDATA_SET_TYPEOF enum values.
named set can be configured as follows:
set os {
type typeof(osf name)
elements = { "Linux", "Windows" }
}
or
nft add set ip filter allowed "{ type typeof(ip daddr) . typeof(tcp dport); }"
... which is the same as the "old" 'type ipv4_addr . inet_service".
The type is stored in the kernel via the udata set infrastructure,
on listing -- if a udata type is present -- nft will validate that this
type matches the set key length.
This initial submission doesn't include a documentation update because
I'd like to get feedback on the chosen syntax first.
Florian Westphal (8):
src: libnftnl: run single-initcalls only once
src: libnftnl: split nft_ctx_new/free
src: store expr, not dtype to track data in sets
src: parser: add syntax to provide bitsize for non-spcific types
src: add "typeof" keyword
src: add "typeof" print support
src: netlink: remove assertion
tests: add typeof test cases
include/datatype.h | 1
include/netlink.h | 1
include/nftables.h | 3
include/rule.h | 6
src/datatype.c | 5
src/evaluate.c | 58 ++++--
src/expression.c | 2
src/json.c | 4
src/libnftables.c | 48 +++--
src/mnl.c | 39 ++++
src/monitor.c | 2
src/netlink.c | 176 ++++++++++++++++++---
src/netlink_delinearize.c | 15 +
src/parser_bison.y | 26 ++-
src/parser_json.c | 8
src/rule.c | 35 +++-
src/scanner.l | 1
src/segtree.c | 8
tests/shell/testcases/maps/dumps/typeof_maps_0.nft | 16 +
tests/shell/testcases/maps/typeof_maps_0 | 26 +++
tests/shell/testcases/sets/dumps/typeof_sets_0.nft | 31 +++
tests/shell/testcases/sets/typeof_sets_0 | 40 ++++
22 files changed, 459 insertions(+), 92 deletions(-)
next reply other threads:[~2019-08-16 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 14:42 Florian Westphal [this message]
2019-08-16 14:42 ` [PATCH nftables 1/8] src: libnftnl: run single-initcalls only once Florian Westphal
2019-08-16 14:42 ` [PATCH nftables 2/8] src: libnftnl: split nft_ctx_new/free Florian Westphal
2019-08-16 14:42 ` [PATCH nftables 3/8] src: store expr, not dtype to track data in sets Florian Westphal
2019-08-16 14:42 ` [PATCH nftables 4/8] src: parser: add syntax to provide bitsize for non-spcific types Florian Westphal
2019-08-16 14:42 ` [PATCH nftables 5/8] src: add "typeof" keyword Florian Westphal
2019-08-16 14:42 ` [PATCH nftables 6/8] src: add "typeof" print support Florian Westphal
2019-08-16 14:42 ` [PATCH nftables 7/8] src: netlink: remove assertion Florian Westphal
2019-08-16 14:42 ` [PATCH nftables 8/8] tests: add typeof test cases Florian Westphal
2019-08-17 10:23 ` [PATCH nftables 0/8] add typeof keyword Pablo Neira Ayuso
2019-08-17 10:33 ` Pablo Neira Ayuso
2019-08-17 19:26 ` Florian Westphal
2019-08-17 20:55 ` Florian Westphal
2019-08-18 14:33 ` Arturo Borrero Gonzalez
2019-08-26 9:49 ` 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=20190816144241.11469-1-fw@strlen.de \
--to=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).