> In cases where some ops failed to enqueue, the op session was never being
> reset. This resulted in a segmentation fault when processing ops the
> next time. To fix this, only set the op session after the failure
> condition is checked.
>
> Also, the incorrect ops index was being used for session retrieval when
> dequeueing for the secondary worker.
>
> Fixes: 6812b9bf470e ("crypto/scheduler: use unified session")
>
> Reported-by: Kevin O'Sullivan <[email protected]>
> Signed-off-by: Ciara Power <[email protected]>
Applied to dpdk-next-crypto
Thanks.
