Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Danny Tsen <dtsen@linux.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, stable@vger.kernel.org,
	leitao@debian.org, nayna@linux.ibm.com, appro@cryptogams.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	mpe@ellerman.id.au, ltcgcw@linux.vnet.ibm.com, dtsen@us.ibm.com
Subject: Re: [PATCH v3] crypto: Removing CRYPTO_AES_GCM_P10.
Date: Sun, 22 Sep 2024 15:49:20 -0500	[thread overview]
Message-ID: <4dbb0949-02a9-4f52-b9c5-5939d9004455@linux.ibm.com> (raw)
In-Reply-To: <Zu6SeXGNAqzVJuPS@gondor.apana.org.au>

Thanks Herbert.

-Danny

On 9/21/24 4:31 AM, Herbert Xu wrote:
> On Thu, Sep 19, 2024 at 07:36:37AM -0400, Danny Tsen wrote:
>> Data mismatch found when testing ipsec tunnel with AES/GCM crypto.
>> Disabling CRYPTO_AES_GCM_P10 in Kconfig for this feature.
>>
>> Fixes: fd0e9b3e2ee6 ("crypto: p10-aes-gcm - An accelerated AES/GCM stitched implementation")
>> Fixes: cdcecfd9991f ("crypto: p10-aes-gcm - Glue code for AES/GCM stitched implementation")
>> Fixes: 45a4672b9a6e2 ("crypto: p10-aes-gcm - Update Kconfig and Makefile")
>>
>> Signed-off-by: Danny Tsen <dtsen@linux.ibm.com>
>> ---
>>   arch/powerpc/crypto/Kconfig | 1 +
>>   1 file changed, 1 insertion(+)
> Patch applied.  Thanks.

      reply	other threads:[~2024-09-22 20:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 11:36 [PATCH v3] crypto: Removing CRYPTO_AES_GCM_P10 Danny Tsen
2024-09-20  9:37 ` Kamlesh Gurudasani
2024-09-21  5:16   ` Stephen Rothwell
2024-09-21  9:31 ` Herbert Xu
2024-09-22 20:49   ` Danny Tsen [this message]

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=4dbb0949-02a9-4f52-b9c5-5939d9004455@linux.ibm.com \
    --to=dtsen@linux.ibm.com \
    --cc=appro@cryptogams.org \
    --cc=dtsen@us.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --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 \
    --cc=stable@vger.kernel.org \
    /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