From: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Vitaly Chikunov <vt@altlinux.org>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: ecrdsa - use subsys_initcall instead of module_init
Date: Mon, 30 Nov 2020 14:54:23 +0800 [thread overview]
Message-ID: <df22e694-0a2e-811a-412e-269303c5d27d@linux.alibaba.com> (raw)
In-Reply-To: <20201130022422.GA21049@gondor.apana.org.au>
On 11/30/20 10:24 AM, Herbert Xu wrote:
> On Mon, Nov 30, 2020 at 10:21:56AM +0800, Tianjia Zhang wrote:
>>
>>> That is true only if there are non-generic implementations of
>>> the algorithms, which is not the case here. Please explain the
>>> real reason why this is needed.
>>
>> This is a generic algorithm, the author Vitaly Chikunov has also confirmed
>> it, please consider this patch again.
>
> As I said, the generic algorithm only needs to be loaded early *if*
> there are non-generic implementations.
>
> Cheers,
>
For ecrdsa, there is no reason to advance the initialization to
subsys_init, this is just to make code clean up to have algorithm
initialization uniform with other implementations.
It’s just that I think that in the commit c4741b230597 ("crypto: run
initcalls for generic implementations earlier"), the modification to
ecrdsa happened to be omitted, because from the point of commit time, it
was submitted at the same time as the ecrdsa commits, and it may happen
to be omitted for ecrdsa.
Best regards,
Tianjia
next prev parent reply other threads:[~2020-11-30 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 11:02 Tianjia Zhang
2020-10-15 12:05 ` Herbert Xu
2020-11-30 2:21 ` Tianjia Zhang
2020-11-30 2:24 ` Herbert Xu
2020-11-30 6:54 ` Tianjia Zhang [this message]
2020-12-01 8:37 ` Ard Biesheuvel
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=df22e694-0a2e-811a-412e-269303c5d27d@linux.alibaba.com \
--to=tianjia.zhang@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vt@altlinux.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
all inboxes | Powered by JetHome®