Prevent kernel from adding concatenated ranges if they're not supported
cover Prevent kernel from adding concatenated ranges if they're not supported
This series fixes the nft crash recently reported by Pablo with older (< 5.6) kernels: use the NFT_SET_CONCAT flag whenever we send a set including concatenated ranges, so that kernels not supporting them will not add them altogether, and we won't crash while trying to list the malformed sets that are added as a result.
Stefano Brivio (2):
include: Resync nf_tables.h cache copy
src: Set NFT_SET_CONCAT flag for sets with concatenated ranges
include/linux/netfilter/nf_tables.h | 2 ++ src/evaluate.c | 9 ++++++++- 2 files changed, 10 insertions(+), 1 deletion(-)
Signature · 1 line
2.25.1
PATCH 1/2 include: Resync nf_tables.h cache copy
Get this header in sync with nf.git as of commit ef516e8625dd.
--- include/linux/netfilter/nf_tables.h | 2 ++ 1 file changed, 2 insertions(+)
include/linux/netfilter/nf_tables.h +2 -0
@@ -276,6 +276,7 @@ enum nft_rule_compat_attributes {* @NFT_SET_TIMEOUT: set uses timeouts * @NFT_SET_EVAL: set can be updated from the evaluation path * @NFT_SET_OBJECT: set contains stateful objects +* @NFT_SET_CONCAT: set contains a concatenation */ enum nft_set_flags {NFT_SET_ANONYMOUS =0x1 ,
@@ -285,6 +286,7 @@ enum nft_set_flags {NFT_SET_TIMEOUT =0x10 ,NFT_SET_EVAL =0x20 ,NFT_SET_OBJECT =0x40 , + NFT_SET_CONCAT = 0x80, };/**
Signature · 1 line
2.25.1
PATCH 2/2 src: Set NFT_SET_CONCAT flag for sets with concatenated ranges
In reply to Stefano BrivioPablo reports that nft, after commit 8ac2f3b2fca3 ("src: Add support for concatenated set ranges"), crashes with older kernels (< 5.6) without support for concatenated set ranges: those sets will be sent to the kernel, which adds them without notion of the fact that different concatenated fields are actually included, and nft crashes while trying to list this kind of malformed concatenation.
Use the NFT_SET_CONCAT flag introduced by kernel commit ef516e8625dd ("netfilter: nf_tables: reintroduce the NFT_SET_CONCAT flag") when sets including concatenated ranges are sent to the kernel, so that older kernels (with no knowledge of this flag itself) will refuse set creation.
Note that, in expr_evaluate_set(), we have to check for the presence of the flag, also on empty sets that might carry it in context data, and actually set it in the actual set flags.
--- src/evaluate.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
src/evaluate.c +8 -1
@@ -1382,10 +1382,16 @@ static int expr_evaluate_set(struct eval_ctx *ctx, struct expr **expr) set->size += i->size -1 ; set->set_flags |= i->set_flags;expr_free (i); - }else if (!expr_is_singleton (i)) + }else if (!expr_is_singleton (i)) { set->set_flags |=NFT_SET_INTERVAL ; +if (i->key->etype ==EXPR_CONCAT ) + set->set_flags |=NFT_SET_CONCAT ; + } } +if (ctx->set && ctx->set->flags & (NFT_SET_CONCAT )) + set->set_flags |=NFT_SET_CONCAT ; + set->set_flags |=NFT_SET_CONSTANT ;datatype_set (set, ctx->ectx.dtype);
@@ -3463,6 +3469,7 @@ static int set_evaluate(struct eval_ctx *ctx, struct set *set)memcpy (&set->desc.field_len, &set->key->field_len,sizeof (set->desc.field_len)); set->desc.field_count = set->key->field_count; + set->flags |=NFT_SET_CONCAT ; }if (set_is_datamap (set->flags)) {
Signature · 1 line
2.25.1
Quoted 5 lines · Stefano Brivio
This series fixes the nft crash recently reported by Pablo with older (< 5.6) kernels: use the
NFT_SET_CONCATflag whenever we send a set including concatenated ranges, so that kernels not supporting them will not add them altogether, and we won't crash while trying to list the malformed sets that are added as a result.
Applied, thanks.