net/mlx5: fs, fail conflicting actions
authorMark Bloch <mbloch@nvidia.com>
Mon, 30 May 2022 07:46:59 +0000 (10:46 +0300)
committerSaeed Mahameed <saeedm@nvidia.com>
Wed, 8 Jun 2022 18:39:44 +0000 (11:39 -0700)
commit8fa5e7b20e01042b14f8cd684d2da9b638460c74
treed8b4b2f9111468b947237f5f4bc7b8c4ba1d1dd4
parent8bf94e6414c9481bfa28269022688ab445d0081d
net/mlx5: fs, fail conflicting actions

When combining two steering rules into one check
not only do they share the same actions but those
actions are also the same. This resolves an issue where
when creating two different rules with the same match
the actions are overwritten and one of the rules is deleted
a FW syndrome can be seen in dmesg.

mlx5_core 0000:03:00.0: mlx5_cmd_check:819:(pid 2105): DEALLOC_MODIFY_HEADER_CONTEXT(0x941) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x1ab444)

Fixes: 0d235c3fabb7 ("net/mlx5: Add hash table to search FTEs in a flow-group")
Signed-off-by: Mark Bloch <mbloch@nvidia.com>
Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c