From: Patrick McHardy <kaber@trash.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 00/10] nftables: set timeouts and dynamic updates
Date: Sun, 12 Apr 2015 13:16:08 +0100 [thread overview]
Message-ID: <1428840978-27226-1-git-send-email-kaber@trash.net> (raw)
The following patches contain support for the new features that have
already been merged to net-next, namely
* set and set element timeouts
* set element comments
* dynamic set updates
The first patch fixes parsing of the time time, the second one relaxes
time parsing. The third and fourth patches add support for time
specification as parameters to the grammar.
The fifth patch fixes inconsistencies in the set greammar, the six
patch adds a generic set element that will be used to attach element
attributes to expressions.
Finally, the seventh patch adds support for set timeouts, the eighth
patch for set element timeouts, the ninth for set element comments.
The last patch adds support for the "set" statement for dynamic set
updates.
I'll give them some more testing and will then push them to a -next
branch in the nftables tree.
Comments, especially regarding the syntax, are welcome.
Patrick McHardy (10):
datatype: fix parsing of time type
datatype: less strict time parsing
datatype: seperate time parsing/printing from time_type
parser: add a time_spec rule
parser: fix inconsistencies in set expression rules
expr: add set_elem_expr as container for set element attributes
set: add timeout support for sets
setelem: add timeout support for set elements
setelem: add support for attaching comments to set elements
nftables: add set statement
include/datatype.h | 4 ++
include/expression.h | 11 ++++
include/linux/netfilter/nf_tables.h | 39 ++++++++++++++
include/rule.h | 5 ++
include/statement.h | 11 ++++
src/datatype.c | 82 ++++++++++++++--------------
src/evaluate.c | 47 +++++++++++++++-
src/expression.c | 42 +++++++++++++++
src/netlink.c | 83 +++++++++++++++++++---------
src/netlink_delinearize.c | 41 ++++++++++++++
src/netlink_linearize.c | 26 +++++++++
src/parser_bison.y | 105 +++++++++++++++++++++++++++++++-----
src/rule.c | 23 +++++++-
src/scanner.l | 10 ++++
src/segtree.c | 8 ++-
src/statement.c | 31 +++++++++++
16 files changed, 486 insertions(+), 82 deletions(-)
--
2.1.0
next reply other threads:[~2015-04-12 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 12:16 Patrick McHardy [this message]
2015-04-12 12:16 ` [PATCH 01/10] datatype: fix parsing of time type Patrick McHardy
2015-04-12 12:16 ` [PATCH 02/10] datatype: less strict time parsing Patrick McHardy
2015-04-12 12:16 ` [PATCH 03/10] datatype: seperate time parsing/printing from time_type Patrick McHardy
2015-04-12 12:16 ` [PATCH 04/10] parser: add a time_spec rule Patrick McHardy
2015-04-12 12:16 ` [PATCH 05/10] parser: fix inconsistencies in set expression rules Patrick McHardy
2015-04-12 12:16 ` [PATCH 06/10] expr: add set_elem_expr as container for set element attributes Patrick McHardy
2015-04-12 12:16 ` [PATCH 07/10] set: add timeout support for sets Patrick McHardy
2015-04-12 12:16 ` [PATCH 08/10] setelem: add timeout support for set elements Patrick McHardy
2015-04-12 12:16 ` [PATCH 09/10] setelem: add support for attaching comments to " Patrick McHardy
2015-04-12 12:16 ` [PATCH 10/10] nftables: add set statement Patrick McHardy
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=1428840978-27226-1-git-send-email-kaber@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).