Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kamlesh Gurudasani <kamlesh@ti.com>
Cc: Danny Tsen <dtsen@linux.ibm.com>, <linux-crypto@vger.kernel.org>,
	<stable@vger.kernel.org>, <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>, <mpe@ellerman.id.au>,
	<ltcgcw@linux.vnet.ibm.com>, <dtsen@us.ibm.com>
Subject: Re: [PATCH v3] crypto: Removing CRYPTO_AES_GCM_P10.
Date: Sat, 21 Sep 2024 15:16:42 +1000	[thread overview]
Message-ID: <20240921151642.60b89e86@canb.auug.org.au> (raw)
In-Reply-To: <87ldzmll80.fsf@kamlesh.i-did-not-set--mail-host-address--so-tickle-me>

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

Hi Kamlesh,

On Fri, 20 Sep 2024 15:07:19 +0530 Kamlesh Gurudasani <kamlesh@ti.com> wrote:
>
> Danny Tsen <dtsen@linux.ibm.com> writes:
> 
> > 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>  
> nitpick
> checkpatch complains
> Please use correct Fixes: style 'Fixes: <12 chars of sha1> ("<title line>")' -
> ie: 'Fixes: 45a4672b9a6e ("crypto: p10-aes-gcm - Update Kconfig and
> Makefile")'
> 
> There is no rule for 12 characters, but it is generally preferred.
> I guess it is just a typo for you as you have correctly added other
> Fixes tag.

It should be at least 12 hex digits i.e. more is fine.  It is possible
that some commits need more than 12 hex digits of the SHA1 to be
uniquely identified in some git repositories already.  I guess
checkpatch needs a patch.

> Also, just to understand,
> 
> "A Fixes: tag indicates that the patch fixes an issue in a previous
>  commit. It is used to make it easy to determine where a bug originated,
>  which can help review a bug fix"
> 
> from 
> https://docs.kernel.org/process/submitting-patches.html
> 
> should there not be just single Fixes tag? as bug originated from one
> commit, may be the commit that actually broke the functionality.

While we generally prefer that a patch only fix one bug, it is very
possible that the bug may have been introduced in more than one commit
e.g. in different files.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-09-21  5:16 UTC|newest]

Thread overview: 6+ 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-19 11:46 ` kernel test robot
2024-09-20  9:37 ` Kamlesh Gurudasani
2024-09-21  5:16   ` Stephen Rothwell [this message]
2024-09-21  9:31 ` Herbert Xu
2024-09-22 20:49   ` 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=20240921151642.60b89e86@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=appro@cryptogams.org \
    --cc=dtsen@linux.ibm.com \
    --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 \
    --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