[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df22e694-0a2e-811a-412e-269303c5d27d@linux.alibaba.com>
Date: Mon, 30 Nov 2020 14:54:23 +0800
From: Tianjia Zhang <tianjia.zhang@...ux.alibaba.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Vitaly Chikunov <vt@...linux.org>,
"David S. Miller" <davem@...emloft.net>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] crypto: ecrdsa - use subsys_initcall instead of
module_init
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
Powered by blists - more mailing lists