[dpdk-dev] [PATCH v2 2/2] crypto/aesni-mb: improve security instance setup

De Lara Guarch, Pablo pablo.de.lara.guarch at intel.com
Wed Jul 22 09:58:19 CEST 2020



> -----Original Message-----
> From: Coyle, David <david.coyle at intel.com>
> Sent: Monday, July 20, 2020 1:16 PM
> To: akhil.goyal at nxp.com; Doherty, Declan <declan.doherty at intel.com>; De
> Lara Guarch, Pablo <pablo.de.lara.guarch at intel.com>; Trahe, Fiona
> <fiona.trahe at intel.com>
> Cc: dev at dpdk.org; Ryan, Brendan <brendan.ryan at intel.com>; O'loingsigh,
> Mairtin <mairtin.oloingsigh at intel.com>; Coyle, David <david.coyle at intel.com>
> Subject: [PATCH v2 2/2] crypto/aesni-mb: improve security instance setup
> 
> This patch makes some improvements to the security instance setup for the
> AESNI-MB PMD, as follows:
> - fix potential memory leak where the security instance was not freed if
>   an error occurred later in the device creation
> - tidy-up security instance initialization code by moving it all,
>   including enabling the RTE_CRYPTODEV_FF_SECURITY feature, into one
>   '#ifdef AESNI_MB_DOCSIS_SEC_ENABLED' block
> 
> Fixes: fda5216fba55 ("crypto/aesni_mb: support DOCSIS protocol")
> 
> Signed-off-by: David Coyle <david.coyle at intel.com>

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


More information about the dev mailing list