[PATCH v2] crypto/ipsec_mb: do not dequeue ops after flush

[De Lara Guarch, Pablo]

> -----Original Message-----
> From: Cornu, Marcel D <marcel.d.cornu at intel.com>
> Sent: Monday, November 13, 2023 11:13 AM
> To: Karas, Krzysztof <krzysztof.karas at intel.com>; Ji, Kai <kai.ji at intel.com>; De
> Lara Guarch, Pablo <pablo.de.lara.guarch at intel.com>; Power, Ciara
> <ciara.power at intel.com>
> Cc: dev at dpdk.org; stable at dpdk.org
> Subject: RE: [PATCH v2] crypto/ipsec_mb: do not dequeue ops after flush
> 
> 
> > -----Original Message-----
> > From: Karas, Krzysztof <krzysztof.karas at intel.com>
> > Sent: Monday, November 13, 2023 8:02 AM
> > To: Ji, Kai <kai.ji at intel.com>; De Lara Guarch, Pablo
> > <pablo.de.lara.guarch at intel.com>; Cornu, Marcel D
> > <marcel.d.cornu at intel.com>; Power, Ciara <ciara.power at intel.com>
> > Cc: dev at dpdk.org; Karas, Krzysztof <krzysztof.karas at intel.com>;
> > stable at dpdk.org
> > Subject: [PATCH v2] crypto/ipsec_mb: do not dequeue ops after flush
> >
> > Previously it was possible to increment `processed_jobs` to a value
> > greater than requested `nb_ops`, because after flushing at most
> > `nb_ops` jobs the while loop continued, so `processed_jobs` could
> > still be incremented and it was possible for this variable to be
> > greater than `nb_ops`. If `ops` provided to the function were only
> > `nb_ops` long, then the `aesni_mb_dequeue_burst()` would write to the
> memory outside of `ops` array.
> >
> > Fixes: b50b8b5b38f8 ("crypto/ipsec_mb: use burst API in AESNI")
> > Cc: stable at dpdk.org
> >
> > Signed-off-by: Krzysztof Karas <krzysztof.karas at intel.com>
> 
> Acked-by: Marcel Cornu <marcel.d.cornu at intel.com>

Acked-by: Pablo de Lara <pablo.de.lara.guarch at intel.com>