> -----Original Message----- > From: Karas, Krzysztof <[email protected]> > Sent: Monday, November 13, 2023 8:02 AM > To: Ji, Kai <[email protected]>; De Lara Guarch, Pablo > <[email protected]>; Cornu, Marcel D > <[email protected]>; Power, Ciara <[email protected]> > Cc: [email protected]; Karas, Krzysztof <[email protected]>; > [email protected] > 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: [email protected] > > Signed-off-by: Krzysztof Karas <[email protected]>
Acked-by: Marcel Cornu <[email protected]>
