[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87seu4qmv6.fsf@mail.lhotse>
Date: Fri, 13 Sep 2024 13:00:13 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: Danny Tsen <dtsen@...ux.ibm.com>, linux-crypto@...r.kernel.org
Cc: herbert@...dor.apana.org.au, leitao@...ian.org, nayna@...ux.ibm.com,
appro@...ptogams.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, ltcgcw@...ux.vnet.ibm.com,
dtsen@...ibm.com, Danny Tsen <dtsen@...ux.ibm.com>
Subject: Re: [PATCH 1/1] crypto: Fix data mismatch over ipsec tunnel
encrypted/decrypted with ppc64le AES/GCM module.
Danny Tsen <dtsen@...ux.ibm.com> writes:
> This patch is to fix an issue when simd is not usable that data mismatch
> may occur over ipsec tunnel. The fix is to register algs as SIMD modules
> so that the algorithm is excecuted when SIMD instructions is usable.
>
> A new module rfc4106(gcm(aes)) is also added. Re-write AES/GCM assembly
> codes with smaller footprints and small performance gain.
>
> This patch has been tested with the kernel crypto module tcrypt.ko and
> has passed the selftest. The patch is also tested with
> CONFIG_CRYPTO_MANAGER_EXTRA_TESTS enabled.
>
> Signed-off-by: Danny Tsen <dtsen@...ux.ibm.com>
> ---
> arch/powerpc/crypto/Kconfig | 1 +
> arch/powerpc/crypto/aes-gcm-p10-glue.c | 141 +-
> arch/powerpc/crypto/aes-gcm-p10.S | 2421 +++++++++++-------------
> 3 files changed, 1187 insertions(+), 1376 deletions(-)
As this is a bug fix it should have a Fixes: tag, and probably a stable
Cc as well.
But that diffstat is really large for a bug fix. Is there no way to fix
the issue in a smaller patch? Even if that is just disabling the feature
until it can be fixed in subsequent commits?
cheers
Powered by blists - more mailing lists