From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH nft,v2 4/8] evaluate: get length from statement instead of lhs expression
Date: Wed, 22 Mar 2023 22:52:59 +0100 [thread overview]
Message-ID: <20230322215303.239763-5-pablo@netfilter.org> (raw)
In-Reply-To: <20230322215303.239763-1-pablo@netfilter.org>
Get length from statement, instead infering it from the expression that
is used to set the value. In the particular case of {ct|meta} mark, this
is 32 bits.
Otherwise, bytecode generation is not correct:
# nft -c --debug=netlink 'add rule ip6 x y ct mark set ip6 dscp << 2 | 0x10'
[ payload load 2b @ network header + 0 => reg 1 ]
[ bitwise reg 1 = ( reg 1 & 0x0000c00f ) ^ 0x00000000 ]
[ bitwise reg 1 = ( reg 1 >> 0x00000006 ) ]
[ byteorder reg 1 = ntoh(reg 1, 2, 1) ]
[ bitwise reg 1 = ( reg 1 << 0x00000002 ) ]
[ bitwise reg 1 = ( reg 1 & 0x00000fef ) ^ 0x00000010 ] <--- incorrect!
[ ct set mark with reg 1 ]
the previous bitwise shift already upgraded to 32-bits (not visible from
the netlink debug output above).
After this patch, the last | 0x10 uses 32-bits:
[ bitwise reg 1 = ( reg 1 & 0xffffffef ) ^ 0x00000010 ]
note that mask 0xffffffef is used instead of 0x00000fef.
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---
src/evaluate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/evaluate.c b/src/evaluate.c
index dfb1236e3b8a..613daa974971 100644
--- a/src/evaluate.c
+++ b/src/evaluate.c
@@ -1325,7 +1325,7 @@ static int expr_evaluate_bitwise(struct eval_ctx *ctx, struct expr **expr)
op->dtype = left->dtype;
op->byteorder = left->byteorder;
- op->len = left->len;
+ op->len = ctx->ectx.len;
if (expr_is_constant(left))
return constant_binop_simplify(ctx, expr);
--
2.30.2
next prev parent reply other threads:[~2023-03-22 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 21:52 [PATCH nft,v2 0/8] mark statement support for non-constant expression Pablo Neira Ayuso
2023-03-22 21:52 ` [PATCH nft,v2 1/8] netlink_delinearize: correct type and byte-order of shifts Pablo Neira Ayuso
2023-03-22 21:52 ` [PATCH nft,v2 2/8] evaluate: support shifts larger than the width of the left operand Pablo Neira Ayuso
2023-03-22 21:52 ` [PATCH nft,v2 3/8] evaluate: don't eval unary arguments Pablo Neira Ayuso
2023-03-22 21:52 ` Pablo Neira Ayuso [this message]
2023-03-22 21:53 ` [PATCH nft,v2 5/8] evaluate: relax type-checking for integer arguments in mark statements Pablo Neira Ayuso
2023-03-22 21:53 ` [PATCH nft,v2 6/8] tests: py: add test-cases for ct and packet mark payload expressions Pablo Neira Ayuso
2023-03-22 21:53 ` [PATCH nft,v2 7/8] tests: shell: rename and move bitwise test-cases Pablo Neira Ayuso
2023-03-22 21:53 ` [PATCH nft,v2 8/8] tests: shell: add test-cases for ct and packet mark payload expressions 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=20230322215303.239763-5-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.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