linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "yekai(A)" <yekai13@huawei.com>
To: <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<wangzhou1@hisilicon.com>, <liulongfang@huawei.com>
Subject: Re: [PATCH v3 0/6] crypto: hisilicon - supports hash algorithm for SEC engine
Date: Sat, 30 Oct 2021 09:06:15 +0800	[thread overview]
Message-ID: <f0f54c23-dec3-f3eb-3283-3ef6478efe33@huawei.com> (raw)
In-Reply-To: <20211022091055.15369-1-yekai13@huawei.com>



On 2021/10/22 17:10, Kai Ye wrote:
> The driver adds hash algorithms, sm3, md5, sha1,
> sha256, sha512. Add fallback tfm supporting. Modify
> the driver as needed. The fuzzing test has been passed.
>
> changes v1->v2:
> 	1. Modify the process of export and import. Using the ahash_req as
> 	   hash state. By copying the content of structure sec_ahash_req to
> 	   avoid dereferencing random pointers from import path. User can
> 	   export the hash state and then import the hash state, and it
> 	   still work.
> 	2. Add sm3/md5 generic selection
> 	
> changes v2->v3:
> 	1. Modify the process of export and import. Export the block of hash
> 	   state from the mac address, then user can import the existing hash
> 	   state.
>
> Kai Ye (6):
>   crypto: hisilicon/sec - add ping-pong buffer for ahash
>   crypto: hisilicon/sec - add ahash alg features for Kunpeng920
>   crypto: hisilicon/sec - support the larger packets for digest mode
>   crypto: hisilicon/sec - ahash adapt to Kunpeng930 SQE
>   crypto: hisilicon/sec - add fallback tfm supporting for ahash
>   crypto: hisilicon/sec - add sm3/md5 generic selection for ahash
>
>  drivers/crypto/hisilicon/Kconfig           |    2 +
>  drivers/crypto/hisilicon/sec2/sec.h        |   56 +-
>  drivers/crypto/hisilicon/sec2/sec_crypto.c | 1345 +++++++++++++++++++-
>  drivers/crypto/hisilicon/sec2/sec_crypto.h |   10 +
>  4 files changed, 1396 insertions(+), 17 deletions(-)
>


Hi Herbert

Could you help to take this patchset?

Thanks

Kai

  parent reply	other threads:[~2021-10-30  1:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  9:10 [PATCH v3 0/6] crypto: hisilicon - supports hash algorithm for SEC engine Kai Ye
2021-10-22  9:10 ` [PATCH v3 1/6] crypto: hisilicon/sec - add ping-pong buffer for ahash Kai Ye
2021-10-22  9:10 ` [PATCH v3 2/6] crypto: hisilicon/sec - add ahash alg features for Kunpeng920 Kai Ye
2021-11-13  6:01   ` Herbert Xu
2021-10-22  9:10 ` [PATCH v3 3/6] crypto: hisilicon/sec - support the larger packets for digest mode Kai Ye
2021-10-22  9:10 ` [PATCH v3 4/6] crypto: hisilicon/sec - ahash adapt to Kunpeng930 SQE Kai Ye
2021-10-22  9:10 ` [PATCH v3 5/6] crypto: hisilicon/sec - add fallback tfm supporting for ahash Kai Ye
2021-10-22  9:10 ` [PATCH v3 6/6] crypto: hisilicon/sec - add sm3/md5 generic selection " Kai Ye
2021-10-30  1:06 ` yekai(A) [this message]
2021-11-02  3:52   ` [PATCH v3 0/6] crypto: hisilicon - supports hash algorithm for SEC engine Herbert Xu

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=f0f54c23-dec3-f3eb-3283-3ef6478efe33@huawei.com \
    --to=yekai13@huawei.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liulongfang@huawei.com \
    --cc=wangzhou1@hisilicon.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;
as well as URLs for NNTP newsgroup(s).