Hi,
> -----Original Message-----
> From: Alex Vesker <va...@nvidia.com>
> Sent: Monday, November 7, 2022 12:18 PM
> To: Alex Vesker <va...@nvidia.com>; Slava Ovsiienko
> <viachesl...@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> <tho...@monjalon.net>; Suanming Mou <suanmi...@nvidia.com>;
> Matan Azrad <ma...@nvidia.com>
> Cc: dev@dpdk.org; Ori Kam <or...@nvidia.com>
> Subject: [PATCH v2] net/mlx5/hws: fix possible action setter segmenation
> fault
>
> When the maximum action combination in RX is used we can get a segfault
> due to an incorrecrt max array size define.
> This bug can happen on RX/TX or FDB in the most complex cases.
> Current max was set to 7, but actual max is:
> Max TX: 8, Max RX: 10, Max FDB: 9
>
> Fixes: f8c8a6d ("net/mlx5/hws: add action object")
missing empty line - will handle during integration
> Signed-off-by: Alex Vesker <va...@nvidia.com>
> Reviewed-by: Erez Shitrit <ere...@nvidia.com>
> Acked-by: Matan Azrad <ma...@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
