tests/shell/testcases/flowtable/0001flowtable_0
tests/shell/testcases/nft-f/0008split_tables_0
fail the 'dump compare' on s390x.
The priority (10) turns to 0, and accept turned to drop.
Problem is that '$1' is a 64bit value -- then we pass the address
and import 'int' -- we then get the upper all zero bits.
Use an intermediate value instead.
Fixes: 627c451b2351 ("src: allow variables in the chain priority specification")
Fixes: dba4a9b4b5fe ("src: allow variable in chain policy")
Signed-off-by: Florian Westphal <fw@xxxxxxxxx>
---
src/parser_bison.y | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/parser_bison.y b/src/parser_bison.y
index 939b9a8db6d7..406cf54bdeb8 100644
--- a/src/parser_bison.y
+++ b/src/parser_bison.y
@@ -1972,11 +1972,12 @@ extended_prio_name : OUT
extended_prio_spec : int_num
{
struct prio_spec spec = {0};
+ int value = (int)$1;
spec.expr = constant_expr_alloc(&@$, &integer_type,
BYTEORDER_HOST_ENDIAN,
sizeof(int) *
- BITS_PER_BYTE, &$1);
+ BITS_PER_BYTE, &value);
$$ = spec;
}
| variable_expr
@@ -2052,10 +2053,12 @@ policy_expr : variable_expr
}
| chain_policy
{
+ int value = (int)$1;
+
$$ = constant_expr_alloc(&@$, &integer_type,
BYTEORDER_HOST_ENDIAN,
sizeof(int) *
- BITS_PER_BYTE, &$1);
+ BITS_PER_BYTE, &value);
}
;
--
2.21.0
