On 20-Oct-26 10:11 AM, Anatoly Burakov wrote:
Egress security flows bypass the flow parsers and are inserted with a NULL `engine` pointer. The create path then dereferences that pointer when logging the new flow, and other engine-based operations cannot handle the flow consistently.Register an egress security engine and route these flows through the normal parser and lifecycle callbacks. Egress flows own no rule and require no hardware teardown. Fixes: e783da175250 ("net/iavf: fix memory leak on egress IPsec flows") Cc:[email protected] Signed-off-by: Anatoly Burakov<[email protected]> ---
Acked-by: Radu Nicolau <[email protected]>
