From d2c364b3db021c120540e77aceeb94e31b57e8db Mon Sep 17 00:00:00 2001 From: Christoph Anton Mitterer Date: Sun, 19 Oct 2025 03:38:09 +0200 Subject: [PATCH] =?utf8?q?doc:=20minor=20improvements=20with=20respect=20t?= =?utf8?q?o=20the=20term=20=E2=80=9Cruleset=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Statements are elements of rules. Non-terminal statement are in particular passive with respect to their rules (and thus automatically with respect to the whole ruleset). In “Continue ruleset evaluation”, it’s not necessary to mention the ruleset as it’s obvious that the evaluation of the current chain will be continued. Signed-off-by: Christoph Anton Mitterer Signed-off-by: Florian Westphal --- doc/nft.txt | 2 +- doc/statements.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/nft.txt b/doc/nft.txt index 78dbef66..2ca601b1 100644 --- a/doc/nft.txt +++ b/doc/nft.txt @@ -932,7 +932,7 @@ actions, such as logging, rejecting a packet, etc. + Statements exist in two kinds. Terminal statements unconditionally terminate evaluation of the current rule, non-terminal statements either only conditionally or never terminate evaluation of the current rule, in other words, -they are passive from the ruleset evaluation perspective. There can be an +they are passive from the rule evaluation perspective. There can be an arbitrary amount of non-terminal statements in a rule, but only a single terminal statement as the final statement. diff --git a/doc/statements.txt b/doc/statements.txt index 834f95fb..e275ee39 100644 --- a/doc/statements.txt +++ b/doc/statements.txt @@ -25,7 +25,7 @@ are not evaluated anymore for the packet. *queue*:: Terminate ruleset evaluation and queue the packet to userspace. Userspace must provide a drop or accept verdict. In case of accept, processing resumes with the next base chain hook, not the rule following the queue verdict. -*continue*:: Continue ruleset evaluation with the next rule. This +*continue*:: Continue evaluation with the next rule. This is the default behaviour in case a rule issues no verdict. *return*:: Return from the current chain and continue evaluation at the next rule in the last chain. If issued in a base chain, it is equivalent to the -- 2.47.3