> -----Original Message-----
> From: Gregory Etelson <[email protected]>
> Sent: Wednesday, November 11, 2020 9:14
> To: [email protected]
> Cc: Gregory Etelson <[email protected]>; Matan Azrad
> <[email protected]>; Raslan Darawsheh <[email protected]>; Shahaf
> Shuler <[email protected]>; Slava Ovsiienko <[email protected]>;
> Xueming(Steven) Li <[email protected]>
> Subject: [PATCH 3/4] net/mlx5: fix PMD crash after tunnel offload match rule
> destruction
>
> The new flow table resource management API triggered a PMD crash in tunnel
> offload mode, when tunnel match flow rule was inserted before tunnel set
> rule.
>
> Reason for the crash was double flow table registration. The table was
> registered by the tunnel offload code for the first time and once more by PMD
> code, as part of general table processing. The table counter was decremented
> only once during the rule destruction and caused a resource leak that
> triggered
> the crash.
>
> The patch updates PMD registration with tunnel offload parameters and
> removes table registration in tunnel related code.
>
> Fixes: 663ad57dabb2 ("net/mlx5: make flow table cache thread safe")
>
> Signed-off-by: Gregory Etelson <[email protected]>
Acked-by: Viacheslav Ovsiienko <[email protected]>