From: Fernando Fernandez Mancera <ffmancera@riseup.net>
To: netfilter-devel@vger.kernel.org
Cc: Fernando Fernandez Mancera <ffmancera@riseup.net>
Subject: [PATCH 0/2 nft v4] Introduce variables in chain priority and policy
Date: Fri, 2 Aug 2019 12:12:06 +0200 [thread overview]
Message-ID: <20190802101207.27719-1-ffmancera@riseup.net> (raw)
This patch series introduces the use of variables in chain priority and policy
specification. It also contains tests for invalid cases.
Closes: https://bugzilla.netfilter.org/show_bug.cgi?id=1172
Fernando Fernandez Mancera (2):
src: allow variables in the chain priority specification
src: allow variable in chain policy
include/datatype.h | 2 +
include/rule.h | 9 +-
src/datatype.c | 65 ++++++++++++++
src/evaluate.c | 85 ++++++++++++++++---
src/json.c | 16 +++-
src/mnl.c | 22 +++--
src/netlink.c | 30 +++++--
src/parser_bison.y | 58 ++++++++++---
src/parser_json.c | 28 ++++--
src/rule.c | 28 +++---
.../testcases/nft-f/0021priority_variable_0 | 17 ++++
.../testcases/nft-f/0022priority_variable_0 | 17 ++++
.../testcases/nft-f/0023priority_variable_1 | 18 ++++
.../testcases/nft-f/0024priority_variable_1 | 18 ++++
.../testcases/nft-f/0025policy_variable_0 | 17 ++++
.../testcases/nft-f/0026policy_variable_0 | 17 ++++
.../testcases/nft-f/0027policy_variable_1 | 18 ++++
.../testcases/nft-f/0028policy_variable_1 | 18 ++++
.../nft-f/dumps/0021priority_variable_0.nft | 5 ++
.../nft-f/dumps/0022priority_variable_0.nft | 5 ++
.../nft-f/dumps/0025policy_variable_0.nft | 5 ++
.../nft-f/dumps/0026policy_variable_0.nft | 5 ++
22 files changed, 439 insertions(+), 64 deletions(-)
mode change 100644 => 100755 src/evaluate.c
create mode 100755 tests/shell/testcases/nft-f/0021priority_variable_0
create mode 100755 tests/shell/testcases/nft-f/0022priority_variable_0
create mode 100755 tests/shell/testcases/nft-f/0023priority_variable_1
create mode 100755 tests/shell/testcases/nft-f/0024priority_variable_1
create mode 100755 tests/shell/testcases/nft-f/0025policy_variable_0
create mode 100755 tests/shell/testcases/nft-f/0026policy_variable_0
create mode 100755 tests/shell/testcases/nft-f/0027policy_variable_1
create mode 100755 tests/shell/testcases/nft-f/0028policy_variable_1
create mode 100644 tests/shell/testcases/nft-f/dumps/0021priority_variable_0.nft
create mode 100644 tests/shell/testcases/nft-f/dumps/0022priority_variable_0.nft
create mode 100644 tests/shell/testcases/nft-f/dumps/0025policy_variable_0.nft
create mode 100644 tests/shell/testcases/nft-f/dumps/0026policy_variable_0.nft
--
2.20.1
next reply other threads:[~2019-08-02 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 10:12 Fernando Fernandez Mancera [this message]
2019-08-02 10:12 ` [PATCH 1/2 nft v4] src: allow variables in the chain priority specification Fernando Fernandez Mancera
2019-08-02 10:12 ` [PATCH 2/2 nft v4] src: allow variable in chain policy Fernando Fernandez Mancera
2019-08-08 10:45 ` [PATCH 0/2 nft v4] Introduce variables in chain priority and policy 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=20190802101207.27719-1-ffmancera@riseup.net \
--to=ffmancera@riseup.net \
--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).