From: "Michael S. Tsirkin" <mst@redhat.com>
To: Lei He <helei.sig11@bytedance.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
dhowells@redhat.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, berrange@redhat.com,
pizhenwei@bytedance.com
Subject: Re: [PATCH v2 0/4] virtio-crypto: support ECDSA algorithm
Date: Fri, 24 Jun 2022 02:51:24 -0400 [thread overview]
Message-ID: <20220624025114-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220623070550.82053-1-helei.sig11@bytedance.com>
On Thu, Jun 23, 2022 at 03:05:46PM +0800, Lei He wrote:
> From: lei he <helei.sig11@bytedance.com>
>
> This patch supports the ECDSA algorithm for virtio-crypto.
virtio parts:
Acked-by: Michael S. Tsirkin <mst@redhat.com>
> V1 -> V2:
> - explicitly specified an appropriate base commit.
> - fixed the link error reported by kernel test robot <lkp@intl.com>.
> - removed irrelevant commits.
>
> V1:
> - fixed the problem that the max_signature_size of ECDSA is
> incorrectly calculated.
> - make pkcs8_private_key_parser can identify ECDSA private keys.
> - implement ECDSA algorithm for virtio-crypto device
>
>
> lei he (4):
> crypto: fix the calculation of max_size for ECDSA
> crypto: pkcs8 parser support ECDSA private keys
> crypto: remove unused field in pkcs8_parse_context
> virtio-crypto: support ECDSA algorithm
>
> crypto/Kconfig | 1 +
> crypto/Makefile | 2 +
> crypto/akcipher.c | 10 +
> crypto/asymmetric_keys/pkcs8.asn1 | 2 +-
> crypto/asymmetric_keys/pkcs8_parser.c | 46 +++-
> crypto/ecdsa.c | 3 +-
> crypto/ecdsa_helper.c | 45 +++
> drivers/crypto/virtio/Kconfig | 1 +
> .../virtio/virtio_crypto_akcipher_algs.c | 259 ++++++++++++++++--
> include/crypto/internal/ecdsa.h | 15 +
> include/linux/asn1_encoder.h | 2 +
> lib/asn1_encoder.c | 3 +-
> 12 files changed, 361 insertions(+), 28 deletions(-)
> create mode 100644 crypto/ecdsa_helper.c
> create mode 100644 include/crypto/internal/ecdsa.h
>
>
> base-commit: 018ab4fabddd94f1c96f3b59e180691b9e88d5d8
> --
> 2.20.1
next prev parent reply other threads:[~2022-06-24 6:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 7:05 [PATCH v2 0/4] virtio-crypto: support ECDSA algorithm Lei He
2022-06-23 7:05 ` [PATCH v2 1/4] crypto: fix the calculation of max_size for ECDSA Lei He
2022-06-23 7:05 ` [PATCH v2 2/4] crypto: pkcs8 parser support ECDSA private keys Lei He
2022-06-23 7:05 ` [PATCH v2 3/4] crypto: remove unused field in pkcs8_parse_context Lei He
2022-06-23 7:05 ` [PATCH v2 4/4] virtio-crypto: support ECDSA algorithm Lei He
2022-06-24 6:51 ` Michael S. Tsirkin [this message]
2022-06-30 6:59 ` [PATCH v2 0/4] " Herbert Xu
2022-06-30 7:23 ` [External] " Lei He
2022-06-30 7:41 ` Herbert Xu
2022-06-30 8:30 ` Lei He
2022-06-30 9:07 ` Herbert Xu
2022-06-30 12:44 ` Lei He
2022-06-30 12:50 ` Lei He
2022-06-30 23:12 ` Sandy Harris
2022-07-01 2:54 ` [External] " Lei He
2022-06-30 9:48 ` [External] " Daniel P. Berrangé
2022-06-30 12:43 ` Lei He
2022-08-09 18:36 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 6:09 Lei He
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=20220624025114-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=berrange@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=helei.sig11@bytedance.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pizhenwei@bytedance.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).