[PATCH 22.11] crypto/ipsec_mb: fix incorrectly setting cipher keys
Luca Boccassi
luca.boccassi at gmail.com
Fri Apr 5 16:43:49 CEST 2024
On Fri, 5 Apr 2024 at 11:46, Ciara Power <ciara.power at intel.com> wrote:
>
> The encryption and decryption keys were incorrectly being reset based on
> authentication algorithm after already being set earlier in the code
> based on cipher algorithm.
> In cases when 3DES was used, the keys were being
> incorrectly overwritten.
>
> For CPU path, there is no need to have the keys set for XCBC and CMAC
> cases.
>
> Fixes: 010230a1543b ("crypto/aesni_mb: support Chacha20-Poly1305")
> Fixes: b0a37e8cd2ac ("crypto/ipsec_mb: fix cipher key setting")
> Fixes: a2c6d3f34f90 ("crypto/aesni_mb: support CPU crypto")
>
> Signed-off-by: Ciara Power <ciara.power at intel.com>
> ---
> Cc: pablo.de.lara.guarch at intel.com
> ---
> drivers/crypto/ipsec_mb/pmd_aesni_mb.c | 14 --------------
> 1 file changed, 14 deletions(-)
I have already tagged rc1 - is this fixing a regression introduced in
rc1 itself? If not, how important is it, could it wait for the next
release?
More information about the stable
mailing list