public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>,
	stefanb@linux.ibm.com, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Warning at crypto/testmgr.c:5900, while booting to OS
Date: Mon, 1 Jul 2024 15:49:05 +0100	[thread overview]
Message-ID: <20240701-stress-mongrel-0ce4b3fdcff7@spud> (raw)
In-Reply-To: <85c8e8095d22db8923c10a180d9e91c61ae64c54.camel@kernel.org>

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

Just a passer-by...

On Mon, Jul 01, 2024 at 02:45:28PM +0000, Jarkko Sakkinen wrote:
> On Wed, 2024-06-12 at 12:16 +0530, Venkat Rao Bagalkote wrote:
> > This issue is being caused by the patch: 2fd2a82ccbfc106aec314db6c4bda5e24fd32a22.
> > 
> > After reverting the above patch, issue is not seen.
> 
> $ git show 2fd2a82ccbfc106aec314db6c4bda5e24fd32a22 # [1]
> fatal: bad object 2fd2a82ccbfc106aec314db6c4bda5e24fd32a22
> 
> Unless I made a mistake, for me it really looks like that the commit is
> non-existent.

It's in linux-next I think:
commit 2fd2a82ccbfc106aec314db6c4bda5e24fd32a22
Author: Stefan Berger <stefanb@linux.ibm.com>
Date:   Wed May 29 19:08:26 2024 -0400

    crypto: ecdsa - Use ecc_digits_from_bytes to create hash digits array
    
    Since ecc_digits_from_bytes will provide zeros when an insufficient number
    of bytes are passed in the input byte array, use it to create the hash
    digits directly from the input byte array. This avoids going through an
    intermediate byte array (rawhash) that has the first few bytes filled with
    zeros.
    
    Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2024-07-01 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  6:46 Warning at crypto/testmgr.c:5900, while booting to OS Venkat Rao Bagalkote
2024-06-13 21:01 ` Stefan Berger
2024-07-01 14:45 ` Jarkko Sakkinen
2024-07-01 14:49   ` Conor Dooley [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=20240701-stress-mongrel-0ce4b3fdcff7@spud \
    --to=conor@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jarkko@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanb@linux.ibm.com \
    --cc=venkat88@linux.vnet.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