summaryrefslogtreecommitdiffstats
path: root/INSTALL
diff options
context:
space:
mode:
authorPhil Sutter <phil@nwl.cc>2017-10-25 13:40:29 +0200
committerPablo Neira Ayuso <pablo@netfilter.org>2017-10-26 20:14:24 +0200
commit94a945ffa81b7f1db250e519f0b4b808428ab223 (patch)
tree869b5960a682e6379762db0cd385b4aec52b6c4b /INSTALL
parentf8596968a650c66e0b4d5895b700d03d7518b245 (diff)
libnftables: Get rid of explicit cache flushes
In the past, CLI as a potentially long running process had to make sure it kept it's cache up to date with kernel's rule set. A simple test case is this: | shell a | shell b | | # nft -i | # nft add table ip t | | | nft> list ruleset | | table ip t { | | } | # nft flush ruleset | | | nft> list ruleset | | nft> In order to make sure interactive CLI wouldn't incorrectly list the table again in the second 'list' command, it immediately flushed it's cache after every command execution. This patch eliminates the need for that by making cache updates depend on kernel's generation ID: A cache update stores the current rule set's ID in struct nft_cache, consecutive calls to cache_update() compare that stored value to the current generation ID received from kernel - if the stored value is zero (i.e. no previous cache update did happen) or if it doesn't match the kernel's value (i.e. cache is outdated) the cache is flushed and fully initialized again. Signed-off-by: Phil Sutter <phil@nwl.cc> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'INSTALL')
0 files changed, 0 insertions, 0 deletions