From: liulongfang <liulongfang@huawei.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] crypto: hisilicon - enable new algorithms of SEC
Date: Fri, 5 Feb 2021 10:05:58 +0800 [thread overview]
Message-ID: <e9a38ae0-383c-59f8-345a-f906fb0b0598@huawei.com> (raw)
In-Reply-To: <20210104113347.GA20681@gondor.apana.org.au>
On 2021/1/4 19:33, Herbert Xu Wrote:
> On Mon, Jan 04, 2021 at 04:15:13PM +0800, liulongfang wrote:
>>
>> Currently, we have not conducted Fuzz testing.
>> For SEC driver, we only adds support for these new algorithms
>> with existing interfaces of Crypto. So, do we need to do Fuzz testing on the existing interfaces?
>
> Please test with SCRYPTO_MANAGER_EXTRA_TEST.
>
> Thanks,
>
After testing with SCRYPTO_MANAGER_EXTRA_TEST, Specifications that our hardware does not support
will cause the test to fail. Before using this patchset,
we need to add software support to solve these problems.
The current patch set needs to be aborted.
Thanks.
prev parent reply other threads:[~2021-02-05 2:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 11:10 [PATCH v2 0/6] crypto: hisilicon - enable new algorithms of SEC Longfang Liu
2020-12-10 11:10 ` [PATCH v2 1/6] crypto: hisilicon/hpre - add version adapt to new algorithms Longfang Liu
2020-12-10 11:10 ` [PATCH v2 2/6] crypto: hisilicon/sec - add new type of sqe for Kunpeng930 Longfang Liu
2020-12-10 11:10 ` [PATCH v2 3/6] crypto: hisilicon/sec - add new skcipher mode for SEC Longfang Liu
2020-12-10 11:10 ` [PATCH v2 4/6] crypto: hisilicon/sec - add new AEAD " Longfang Liu
2020-12-10 11:10 ` [PATCH v2 5/6] crypto: hisilicon/sec - fixes some coding style Longfang Liu
2020-12-10 11:10 ` [PATCH v2 6/6] crypto: hisilicon/sec - add new algorithm test case Longfang Liu
2021-01-02 21:00 ` [PATCH v2 0/6] crypto: hisilicon - enable new algorithms of SEC Herbert Xu
2021-01-04 8:15 ` liulongfang
2021-01-04 11:33 ` Herbert Xu
2021-02-05 2:05 ` liulongfang [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=e9a38ae0-383c-59f8-345a-f906fb0b0598@huawei.com \
--to=liulongfang@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).