linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Danny Tsen <dtsen@linux.ibm.com>
To: Kamlesh Gurudasani <kamlesh@ti.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, leitao@debian.org,
	nayna@linux.ibm.com, appro@cryptogams.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	ltcgcw@linux.vnet.ibm.com, dtsen@us.ibm.com
Subject: Re: [PATCH 1/1] crypto: Fix data mismatch over ipsec tunnel encrypted/decrypted with ppc64le AES/GCM module.
Date: Fri, 13 Sep 2024 06:16:05 -0500	[thread overview]
Message-ID: <83a1ce2f-c633-42cb-92c6-2477cd2e47f2@linux.ibm.com> (raw)
In-Reply-To: <875xr0m5ss.fsf@kamlesh.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]

Yes, checkpath was run.

Not sure what you mean by "some indentation changes.(This can't go with 
fixes patch, will just add the noise)"

Thanks.

On 9/13/24 1:22 AM, Kamlesh Gurudasani wrote:
> Michael Ellerman<mpe@ellerman.id.au> writes:
>
>> Danny Tsen<dtsen@linux.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@linux.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
> The commit message says "The fix is to register algs as SIMD modules"
>
> and
>
> "A new module rfc4106(gcm(aes)) is also added."
>
> and I also see some indentation changes.(This can't go with fixes patch,
> will just add the noise)
>
> Would suggest to break the patch in three.
>
> I see a big subject line, have you ran the checkpatch?
>
> Kamlesh
>

[-- Attachment #2: Type: text/html, Size: 2736 bytes --]

  reply	other threads:[~2024-09-13 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 17:45 [PATCH 1/1] crypto: Fix data mismatch over ipsec tunnel encrypted/decrypted with ppc64le AES/GCM module Danny Tsen
2024-09-13  3:00 ` Michael Ellerman
2024-09-13  6:22   ` Kamlesh Gurudasani
2024-09-13 11:16     ` Danny Tsen [this message]
2024-09-15  6:07       ` Kamlesh Gurudasani
2024-09-13 11:12   ` Danny Tsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83a1ce2f-c633-42cb-92c6-2477cd2e47f2@linux.ibm.com \
    --to=dtsen@linux.ibm.com \
    --cc=appro@cryptogams.org \
    --cc=dtsen@us.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kamlesh@ti.com \
    --cc=leitao@debian.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ltcgcw@linux.vnet.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=nayna@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).