net/mlx5: fix drop action validation
Function mlx5_flow_validate_action_drop() checks if another fate action is already present in this flow rule, using defined value MLX5_FLOW_FATE_ACTIONS. This patch enhances the check using value (MLX5_FLOW_FATE_ACTIONS | MLX5_FLOW_FATE_ESWITCH_ACTIONS) to make sure all relevant fate actions are checked. Fixes: 23c1d42c7138 ("net/mlx5: split flow validation to dedicated function") Cc: stable@dpdk.org Signed-off-by: Dekel Peled <dekelp@mellanox.com> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
This commit is contained in:
parent
48c91c8f3f
commit
e6ed9dfdf8
@ -817,7 +817,8 @@ mlx5_flow_validate_action_drop(uint64_t action_flags,
|
||||
return rte_flow_error_set(error, EINVAL,
|
||||
RTE_FLOW_ERROR_TYPE_ACTION, NULL,
|
||||
"can't drop and mark in same flow");
|
||||
if (action_flags & MLX5_FLOW_FATE_ACTIONS)
|
||||
if (action_flags & (MLX5_FLOW_FATE_ACTIONS |
|
||||
MLX5_FLOW_FATE_ESWITCH_ACTIONS))
|
||||
return rte_flow_error_set(error, EINVAL,
|
||||
RTE_FLOW_ERROR_TYPE_ACTION, NULL,
|
||||
"can't have 2 fate actions in"
|
||||
|
Loading…
x
Reference in New Issue
Block a user