net/mlx5: check maximum modify actions number

[dpdk.git] / drivers / net / mlx5 / mlx5_flow_dv.c

diff --git a/drivers/net/mlx5/mlx5_flow_dv.c b/drivers/net/mlx5/mlx5_flow_dv.c
index 98161d3..5f3ea1f 100644 (file)
--- a/drivers/net/mlx5/mlx5_flow_dv.c
+++ b/drivers/net/mlx5/mlx5_flow_dv.c
@@ -2748,6 +2748,27 @@ flow_dv_validate_action_port_id(struct rte_eth_dev *dev,
        return 0;
 }
 
+/**
+ * Get the maximum number of modify header actions.
+ *
+ * @param dev
+ *   Pointer to rte_eth_dev structure.
+ *
+ * @return
+ *   Max number of modify header actions device can support.
+ */
+static unsigned int
+flow_dv_modify_hdr_action_max(struct rte_eth_dev *dev)
+{
+       /*
+        * There's no way to directly query the max cap. Although it has to be
+        * acquried by iterative trial, it is a safe assumption that more
+        * actions are supported by FW if extensive metadata register is
+        * supported.
+        */
+       return mlx5_flow_ext_mreg_supported(dev) ? MLX5_MODIFY_NUM :
+                                                  MLX5_MODIFY_NUM_NO_MREG;
+}
 /**
  * Find existing modify-header resource or create and register a new one.
  *
@@ -2775,6 +2796,10 @@ flow_dv_modify_hdr_resource_register
        struct mlx5_flow_dv_modify_hdr_resource *cache_resource;
        struct mlx5dv_dr_domain *ns;
 
+       if (resource->actions_num > flow_dv_modify_hdr_action_max(dev))
+               return rte_flow_error_set(error, EOVERFLOW,
+                                         RTE_FLOW_ERROR_TYPE_ACTION, NULL,
+                                         "too many modify header items");
        if (resource->ft_type == MLX5DV_FLOW_TABLE_TYPE_FDB)
                ns = sh->fdb_domain;
        else if (resource->ft_type == MLX5DV_FLOW_TABLE_TYPE_NIC_TX)