From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, Eric Garver <e@erig.me>
Subject: [nft PATCH v5 00/10] Cache update fix && intra-transaction rule references
Date: Tue, 4 Jun 2019 19:31:48 +0200 [thread overview]
Message-ID: <20190604173158.1184-1-phil@nwl.cc> (raw)
Next round of combined cache update fix and intra-transaction rule
reference support.
Patch 2 is new, it avoids accidential cache updates when committing a
transaction containing flush ruleset command and kernel ruleset has
changed meanwhile.
Patch 3 is also new: If a transaction fails in kernel, local cache is
incorrect - drop it.
Patch 9 is a new requirement for patch 10 due to relocation of new
functions.
Patch 10 was changed, changelog included.
Phil Sutter (10):
src: Fix cache_flush() in cache_needs_more() logic
src: Utilize CMD_FLUSH for cache->cmd
libnftables: Drop cache in error case
libnftables: Keep list of commands in nft context
src: Make {table,chain}_not_found() public
src: Restore local entries after cache update
rule: Introduce rule_lookup_by_index()
src: Make cache_is_complete() public
include: Collect __stmt_binary_error() wrapper macros
src: Support intra-transaction rule references
include/erec.h | 6 +
include/nftables.h | 1 +
include/rule.h | 10 +
src/evaluate.c | 71 ++----
src/libnftables.c | 25 ++-
src/mnl.c | 4 +
src/rule.c | 202 +++++++++++++++++-
tests/json_echo/run-test.py | 6 +-
.../shell/testcases/cache/0003_cache_update_0 | 7 +
tests/shell/testcases/transactions/0024rule_0 | 17 ++
tests/shell/testcases/transactions/0025rule_0 | 21 ++
.../transactions/dumps/0024rule_0.nft | 8 +
.../transactions/dumps/0025rule_0.nft | 6 +
13 files changed, 314 insertions(+), 70 deletions(-)
create mode 100755 tests/shell/testcases/transactions/0024rule_0
create mode 100755 tests/shell/testcases/transactions/0025rule_0
create mode 100644 tests/shell/testcases/transactions/dumps/0024rule_0.nft
create mode 100644 tests/shell/testcases/transactions/dumps/0025rule_0.nft
--
2.21.0
next reply other threads:[~2019-06-04 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 17:31 Phil Sutter [this message]
2019-06-04 17:31 ` [nft PATCH v5 01/10] src: Fix cache_flush() in cache_needs_more() logic Phil Sutter
2019-06-06 9:21 ` Pablo Neira Ayuso
2019-06-04 17:31 ` [nft PATCH v5 02/10] src: Utilize CMD_FLUSH for cache->cmd Phil Sutter
2019-06-04 17:31 ` [nft PATCH v5 03/10] libnftables: Drop cache in error case Phil Sutter
2019-06-06 9:21 ` Pablo Neira Ayuso
2019-06-04 17:31 ` [nft PATCH v5 04/10] libnftables: Keep list of commands in nft context Phil Sutter
2019-06-04 17:31 ` [nft PATCH v5 05/10] src: Make {table,chain}_not_found() public Phil Sutter
2019-06-04 17:31 ` [nft PATCH v5 06/10] src: Restore local entries after cache update Phil Sutter
2019-06-04 17:31 ` [nft PATCH v5 07/10] rule: Introduce rule_lookup_by_index() Phil Sutter
2019-06-04 17:31 ` [nft PATCH v5 08/10] src: Make cache_is_complete() public Phil Sutter
2019-06-04 17:31 ` [nft PATCH v5 09/10] include: Collect __stmt_binary_error() wrapper macros Phil Sutter
2019-06-04 17:31 ` [nft PATCH v5 10/10] src: Support intra-transaction rule references Phil Sutter
2019-06-05 17:05 ` [nft PATCH v5 00/10] Cache update fix && " Pablo Neira Ayuso
2019-06-05 19:24 ` Phil Sutter
2019-06-06 8:36 ` Pablo Neira Ayuso
2019-06-06 9:42 ` 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=20190604173158.1184-1-phil@nwl.cc \
--to=phil@nwl.cc \
--cc=e@erig.me \
--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).