numam-dpdk/drivers
Dmitry Kozlyuk 4ec1f971cd net/mlx5: report error on indirect CT action destroy
When an indirect CT action of mlx5 PMD could not be destroyed,
rte_action_handle_destroy() was returning (-1), but the error
structure was not filled. This lead to a segfault in testpmd
on an attempt to print it. Fill the details for each possible
cause of this error.

Fixes: c5a49265fc ("net/mlx5: add ASO connection tracking destroy")
Cc: stable@dpdk.org

Signed-off-by: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
2021-09-21 09:56:12 +02:00
..
baseband version: 21.11-rc0 2021-08-17 08:37:52 +02:00
bus bus/fslmc: move experimental function to internal 2021-09-24 18:44:00 +02:00
common common/mlx5: fix resource cleaning in device removal 2021-09-20 23:22:10 +02:00
compress compress/mlx5: fix leak on QP setup failure 2021-09-06 21:46:34 +02:00
crypto common/cnxk: support tunnel header verification 2021-09-28 17:49:10 +02:00
event cryptodev: expose driver interface as internal 2021-09-08 09:35:12 +02:00
mempool version: 21.11-rc0 2021-08-17 08:37:52 +02:00
net net/mlx5: report error on indirect CT action destroy 2021-09-21 09:56:12 +02:00
raw drivers: remove warning with Meson 0.59 2021-08-27 15:51:34 +02:00
regex regex/mlx5: fix leak after probing failure 2021-09-22 21:21:31 +02:00
vdpa vdpa/mlx5: fix large VM memory region registration 2021-09-27 17:24:22 +02:00
meson.build build: fix essential drivers in disable list 2021-09-15 11:00:15 +02:00