Fix evaluation of anonymous sets with concatenated ranges
v2 cover Fix evaluation of anonymous sets with concatenated ranges
As reported by both Pablo and Phil, trying to add an anonymous set containing a concatenated range would fail:
# nft add rule x y ip saddr . tcp dport { 192.168.2.1 . 20-30 } accept
BUG: invalid range expression type concat
nft: expression.c:1160: range_expr_value_low: Assertion `0' failed.
Aborted # nft add rule t c ip daddr . tcp dport '{ 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443 } accept'
BUG: invalid range expression type concat
nft: expression.c:1296: range_expr_value_low: Assertion `0' failed.Patch 1/2 fixes this, and 2/2 enables a test for it in inet/sets.t.
v2: Don't add anonymous sets to cache, fix leak for object maps, and
use existing test rule instead of adding a new test
Stefano Brivio (2):
evaluate: Perform set evaluation on implicitly declared (anonymous)
sets
tests: py: Enable anonymous set rule with concatenated ranges in
inet/sets.t
src/evaluate.c | 20 ++++++++++---------- tests/py/inet/sets.t | 2 +- tests/py/inet/sets.t.payload.bridge | 14 ++++++++++++++ tests/py/inet/sets.t.payload.inet | 13 +++++++++++++ tests/py/inet/sets.t.payload.netdev | 13 +++++++++++++ 5 files changed, 51 insertions(+), 11 deletions(-)
Signature · 1 line
2.26.2
PATCH v2 2/2 tests: py: Enable anonymous set rule with concatenated ranges in inet/sets.t
Commit 64b9aa3803dd ("tests/py: Add tests involving concatenated ranges") introduced a rule, commented out, adding an anonymous set including concatenated ranges. Now that they are properly handled, we can enable it.
Note that this introduces a new warning. In the output below, '\' marks newlines I introduced to keep lines short:
inet/sets.t: WARNING: line 24: \
'add rule inet test-inet input ip daddr . tcp dport \
{ 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443 } accept': \
'ip daddr . tcp dport \
{ 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443 } accept' \
mismatches 'meta nfproto ipv4 ip daddr . tcp dport \
{ 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443} accept'
which is similar to the existing warning, also introduced by commit 64b9aa3803dd:
inet/sets.t: WARNING: line 23: \
'add rule inet test-inet input \
ip saddr . ip daddr . tcp dport @set3 accept': \
'ip saddr . ip daddr . tcp dport @set3 accept' mismatches \
'meta nfproto ipv4 ip saddr . ip daddr . tcp dport @set3 accept'
This is mentioned in the commit message for 64b9aa3803dd itself:
* Payload dependency killing ignores the concatenated IP header expressions on LHS, so rule output is asymmetric.
which means that for family inet, 'meta nfproto ipv4' is added to the output of the rule, on top of what was passed as input, but not for families bridge and netdev.
For this reason, it's not possible in this case to specify a single expected output, differing from the input, and, also, 'meta nfproto ipv4' can only be passed as input for family inet as it's not relevant for the other families.
As an alternative, we could split the rules from this test into tests for the corresponding families, as this test case itself is under the 'inet' directory, but I consider this beyond the scope of this patchset.
v2: Enable rule in py/inet/sets.t instead of adding a new test in
shell/sets (Phil Sutter)
--- tests/py/inet/sets.t | 2 +- tests/py/inet/sets.t.payload.bridge | 14 ++++++++++++++ tests/py/inet/sets.t.payload.inet | 13 +++++++++++++ tests/py/inet/sets.t.payload.netdev | 13 +++++++++++++ 4 files changed, 41 insertions(+), 1 deletion(-)
tests/py/inet/sets.t +1 -1
@@ -21,4 +21,4 @@ ip6 daddr @set1 drop;fail ?set3 10.0.0.0/8 . 192.168.1.3-192.168.1.9 . 1024-65535;ok ip saddr . ip daddr . tcp dport @set3 accept;ok --ip daddr . tcp dport { 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443 } accept;ok +ip daddr . tcp dport { 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443 } accept;ok
tests/py/inet/sets.t.payload.bridge +14 -0
@@ -26,3 +26,17 @@ bridge [ lookup reg 1 set set3 ] [ immediate reg 0 accept ] +# ip daddr . tcp dport { 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443 } accept +__set%d test-inet 87 +__set%d test-inet 0 + element 0000000a 00000a00 : 0 [end] element 0101a8c0 00005000 : 0 [end] +bridge + [ meta load protocol => reg 1 ] + [ cmp eq reg 1 0x00000008 ] + [ meta load l4proto => reg 1 ] + [ cmp eq reg 1 0x00000006 ] + [ payload load 4b @ network header + 16 => reg 1 ] + [ payload load 2b @ transport header + 2 => reg 9 ] + [ lookup reg 1 set __set%d ] + [ immediate reg 0 accept ] +
tests/py/inet/sets.t.payload.inet +13 -0
@@ -26,3 +26,16 @@ inet [ lookup reg 1 set set3 ] [ immediate reg 0 accept ] +# ip daddr . tcp dport { 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443 } accept +__set%d test-inet 87 +__set%d test-inet 0 + element 0000000a 00000a00 : 0 [end] element 0101a8c0 00005000 : 0 [end] +inet + [ meta load nfproto => reg 1 ] + [ cmp eq reg 1 0x00000002 ] + [ meta load l4proto => reg 1 ] + [ cmp eq reg 1 0x00000006 ] + [ payload load 4b @ network header + 16 => reg 1 ] + [ payload load 2b @ transport header + 2 => reg 9 ] + [ lookup reg 1 set __set%d ] + [ immediate reg 0 accept ]
tests/py/inet/sets.t.payload.netdev +13 -0
@@ -26,3 +26,16 @@ inet [ lookup reg 1 set set3 ] [ immediate reg 0 accept ] +# ip daddr . tcp dport { 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443 } accept +__set%d test-netdev 87 +__set%d test-netdev 0 + element 0000000a 00000a00 : 0 [end] element 0101a8c0 00005000 : 0 [end] +netdev + [ meta load protocol => reg 1 ] + [ cmp eq reg 1 0x00000008 ] + [ meta load l4proto => reg 1 ] + [ cmp eq reg 1 0x00000006 ] + [ payload load 4b @ network header + 16 => reg 1 ] + [ payload load 2b @ transport header + 2 => reg 9 ] + [ lookup reg 1 set __set%d ] + [ immediate reg 0 accept ]
Signature · 1 line
2.26.2
PATCH v2 1/2 evaluate: Perform set evaluation on implicitly declared (anonymous) sets
In reply to Stefano BrivioIf a set is implicitly declared, set_evaluate() is not called as a result of cmd_evaluate_add(), because we're adding in fact something else (e.g. a rule). Expression-wise, evaluation still happens as the implicit set expression is eventually found in the tree and handled by expr_evaluate_set(), but context-wise evaluation (set_evaluate()) is skipped, and this might be relevant instead.
This is visible in the reported case of an anonymous set including concatenated ranges:
# nft add rule t c ip saddr . tcp dport { 192.0.2.1 . 20-30 } accept
BUG: invalid range expression type concat
nft: expression.c:1160: range_expr_value_low: Assertion `0' failed.
Abortedbecause we reach do_add_set() without properly evaluated flags and set description, and eventually end up in expr_to_intervals(), which can't handle that expression.
Explicitly call set_evaluate() as we add anonymous sets into the context, and instruct the same function to:
- skip expression-wise set evaluation if the set is anonymous, as that happens later anyway as part of the general tree evaluation
- skip the insertion in the set cache, as it makes no sense to have sets that shouldn't be referenced there
For object maps, the allocation of the expression for set->data is already handled by set_evaluate(), so we can now drop that from stmt_evaluate_objref_map().
v2:
- skip insertion of set in cache (Pablo Neira Ayuso)
- drop double allocation of expression (and leak of the first one) for object maps (Pablo Neira Ayuso)
--- src/evaluate.c | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-)
src/evaluate.c +10 -10
@@ -76,6 +76,7 @@ static void key_fix_dtype_byteorder(struct expr *key)datatype_set (key,set_datatype_alloc (dtype, key->byteorder)); } +static int set_evaluate (struct eval_ctx *ctx,struct set *set); static struct expr *implicit_set_declaration(struct eval_ctx *ctx, const char *name, struct expr *key,
@@ -107,6 +108,8 @@ static struct expr *implicit_set_declaration(struct eval_ctx *ctx,list_add_tail (&cmd->list, &ctx->cmd->list); } +set_evaluate (ctx, set); +return set_ref_expr_alloc (&expr->location, set); }
@@ -3316,12 +3319,6 @@ static int stmt_evaluate_objref_map(struct eval_ctx *ctx, struct stmt *stmt) mappings =implicit_set_declaration (ctx,"__objmap%d" , key, mappings); - - mappings->set->data =constant_expr_alloc (&netlink_location, - &string_type, -BYTEORDER_HOST_ENDIAN , -NFT_OBJ_MAXNAMELEN *BITS_PER_BYTE , -NULL ); mappings->set->objtype = stmt->objref.type; map->mappings = mappings;
@@ -3546,6 +3543,13 @@ static int set_evaluate(struct eval_ctx *ctx, struct set *set) } +/* Default timeout value implies timeout support */ +if (set->timeout) + set->flags |=NFT_SET_TIMEOUT ; + +if (set_is_anonymous (set->flags)) +return 0 ; + ctx->set = set;if (set->init !=NULL ) { __expr_set_context(&ctx->ectx, set->key->dtype,
@@ -3558,10 +3562,6 @@ static int set_evaluate(struct eval_ctx *ctx, struct set *set)if (set_lookup (table, set->handle.set.name) ==NULL )set_add_hash (set_get (set), table); -/* Default timeout value implies timeout support */ -if (set->timeout) - set->flags |=NFT_SET_TIMEOUT ; -return 0 ; }
Signature · 1 line
2.26.2
Pablo Neira Ayuso
maintainerQuoted 8 lines · Stefano Brivio
As reported by both Pablo and Phil, trying to add an anonymous set containing a concatenated range would fail:
# nft add rule x y ip saddr . tcp dport { 192.168.2.1 . 20-30 } accept BUG: invalid range expression type concat nft: expression.c:1160: range_expr_value_low: Assertion `0' failed. Aborted
Quoted 5 lines
# nft add rule t c ip daddr . tcp dport '{ 10.0.0.0/8 . 10-23, 192.168.1.1-192.168.3.8 . 80-443 } accept' BUG: invalid range expression type concat nft: expression.c:1296: range_expr_value_low: Assertion `0' failed.Patch 1/2 fixes this, and 2/2 enables a test for it in inet/sets.t.
Series applied, thanks Stefano.