From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: fw@strlen.de
Subject: [PATCH nft 00/11] complete typeof support
Date: Tue, 17 Dec 2019 18:16:51 +0100 [thread overview]
Message-ID: <20191217171702.31493-1-pablo@netfilter.org> (raw)
Hi Florian,
This completes your patchset adding typeof support for the remaining
primary expression.
Feel free to apply and push this out on top of your patchset.
P.S: testcases/maps/typeof_maps_0 fails:
/dev/stdin:14:28-30: Error: datatype mismatch, map expects string,
mapping expression has type IPv4 address
ct mark set ip daddr map @m1
~~~~~~~~ ^^^
There is a typo in the map definition:
/dev/stdin:14:28-30: Error: datatype mismatch, map expects string,
mapping expression has type IPv4 address
ct mark set ip daddr map @m1
~~~~~~~~ ^^^
This should be
ct mark set osf name map @m1
dump file also needs an adjustment, you can fix this before pushing
this out.
Thanks!
P.S: I might follow up at some point to expose this userdata
attributes through libnftnl, later. Meanwhile, I have just pushed
out the libnftnl nesting dependencies.
Pablo Neira Ayuso (11):
meta: add parse and build userdata interface
exthdr: add exthdr_desc_id enum and use it
exthdr: add parse and build userdata interface
socket: add parse and build userdata interface
osf: add parse and build userdata interface
ct: add parse and build userdata interface
numgen: add parse and build userdata interface
hash: add parse and build userdata interface
rt: add parse and build userdata interface
fib: add parse and build userdata interface
xfrm: add parse and build userdata interface
include/exthdr.h | 15 ++++++++
src/ct.c | 56 ++++++++++++++++++++++++++++++
src/expression.c | 13 +++++--
src/exthdr.c | 102 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
src/fib.c | 60 ++++++++++++++++++++++++++++++--
src/hash.c | 72 +++++++++++++++++++++++++++++++++++++++
src/meta.c | 51 ++++++++++++++++++++++++++++
src/numgen.c | 62 +++++++++++++++++++++++++++++++++
src/osf.c | 13 +++++++
src/rt.c | 51 ++++++++++++++++++++++++++++
src/socket.c | 51 ++++++++++++++++++++++++++++
src/xfrm.c | 61 +++++++++++++++++++++++++++++++++
12 files changed, 603 insertions(+), 4 deletions(-)
--
2.11.0
next reply other threads:[~2019-12-17 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 17:16 Pablo Neira Ayuso [this message]
2019-12-17 17:16 ` [PATCH nft 01/11] meta: add parse and build userdata interface Pablo Neira Ayuso
2019-12-17 17:16 ` [PATCH nft 02/11] exthdr: add exthdr_desc_id enum and use it Pablo Neira Ayuso
2019-12-17 17:16 ` [PATCH nft 03/11] exthdr: add parse and build userdata interface Pablo Neira Ayuso
2019-12-17 17:16 ` [PATCH nft 04/11] socket: " Pablo Neira Ayuso
2019-12-17 17:16 ` [PATCH nft 05/11] osf: " Pablo Neira Ayuso
2019-12-17 17:16 ` [PATCH nft 06/11] ct: " Pablo Neira Ayuso
2019-12-17 17:16 ` [PATCH nft 07/11] numgen: " Pablo Neira Ayuso
2019-12-17 17:16 ` [PATCH nft 08/11] hash: " Pablo Neira Ayuso
2019-12-17 17:17 ` [PATCH nft 09/11] rt: " Pablo Neira Ayuso
2019-12-17 17:17 ` [PATCH nft 10/11] fib: " Pablo Neira Ayuso
2019-12-17 17:17 ` [PATCH nft 11/11] xfrm: " 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=20191217171702.31493-1-pablo@netfilter.org \
--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