From: Stefan Berger <stefanb@linux.ibm.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-kernel@vger.kernel.org, lukas@wunner.de
Subject: Re: [PATCH v2] crypto: ecc - Prevent ecc_digits_from_bytes from reading too many bytes
Date: Mon, 29 Apr 2024 12:57:21 -0400 [thread overview]
Message-ID: <f001bc3f-0c70-4118-bc71-8455808004b4@linux.ibm.com> (raw)
In-Reply-To: <D0WRD3IZ3AJC.GWZHZLHHBJ5B@kernel.org>
On 4/29/24 12:47, Jarkko Sakkinen wrote:
> On Mon Apr 29, 2024 at 7:13 PM EEST, Stefan Berger wrote:
>> Prevent ecc_digits_from_bytes from reading too many bytes from the input
>> byte array in case an insufficient number of bytes is provided to fill the
>> output digit array of ndigits. Therefore, initialize the most significant
>> digits with 0 to avoid trying to read too many bytes later on. Convert the
>> function into a regular function since it is getting too big for an inline
>> function.
>>
>> If too many bytes are provided on the input byte array the extra bytes
>> are ignored since the input variable 'ndigits' limits the number of digits
>> that will be filled.
>>
>> Fixes: d67c96fb97b5 ("crypto: ecdsa - Convert byte arrays with key coordinates to digits")
>> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
>>
>> ---
>>
>> v2:
>> - un-inline function
>> - use memset
>> ---
>> crypto/ecc.c | 22 ++++++++++++++++++++++
>> include/crypto/internal/ecc.h | 15 ++-------------
>> 2 files changed, 24 insertions(+), 13 deletions(-)
>>
>> diff --git a/crypto/ecc.c b/crypto/ecc.c
>> index c1d2e884be1e..fe761256e335 100644
>> --- a/crypto/ecc.c
>> +++ b/crypto/ecc.c
>> @@ -68,6 +68,28 @@ const struct ecc_curve *ecc_get_curve(unsigned int curve_id)
>> }
>> EXPORT_SYMBOL(ecc_get_curve);
>>
>
> Just a minor nit:
>
> For exported symbol you need to document the function,including
> the parameters [1].
Like other functions, the ecc_digits_from_bytes also still/already has
the documentation in the header file:
/**
* ecc_digits_from_bytes() - Create ndigits-sized digits array from
byte array
* @in: Input byte array
* @nbytes Size of input byte array
* @out Output digits array
* @ndigits: Number of digits to create from byte array
*/
void ecc_digits_from_bytes(const u8 *in, unsigned int nbytes,
u64 *out, unsigned int ndigits);
Should be ok?
next prev parent reply other threads:[~2024-04-29 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 16:13 Stefan Berger
2024-04-29 16:47 ` Jarkko Sakkinen
2024-04-29 16:57 ` Stefan Berger [this message]
2024-04-29 17:07 ` Jarkko Sakkinen
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=f001bc3f-0c70-4118-bc71-8455808004b4@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
/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
all inboxes | Powered by JetHome®