From: "Michael S. Tsirkin" <mst@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.com>
Cc: herbert@gondor.apana.org.au, cohuck@redhat.com,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, helei.sig11@bytedance.com
Subject: Re: [PATCH v3 0/4] Introduce akcipher service for virtio-crypto
Date: Mon, 7 Mar 2022 04:05:37 -0500 [thread overview]
Message-ID: <20220307040431-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <a9d1dfc1-080e-fba2-8fbb-28718b067e0d@bytedance.com>
On Mon, Mar 07, 2022 at 10:42:30AM +0800, zhenwei pi wrote:
> Hi, Michael & Lei
>
> The full patchset has been reviewed by Gonglei, thanks to Gonglei.
> Should I modify the virtio crypto specification(use "__le32 akcipher_algo;"
> instead of "__le32 reserve;" only, see v1->v2 change), and start a new issue
> for a revoting procedure?
You can but not it probably will be deferred to 1.3. OK with you?
> Also cc Cornelia Huck.
>
> On 3/2/22 11:39 AM, zhenwei pi wrote:
> > v2 -> v3:
> > Rename virtio_crypto_algs.c to virtio_crypto_skcipher_algs.c, and
> > minor changes of function name.
> > Minor changes in virtio_crypto_akcipher_algs.c: no need to copy from
> > buffer if opcode is verify.
> >
> > v1 -> v2:
> > Fix 1 compiling warning reported by kernel test robot <lkp@intel.com>
> > Put "__le32 akcipher_algo;" instead of "__le32 reserve;" field of
> > struct virtio_crypto_config directly without size change.
> > Add padding in struct virtio_crypto_ecdsa_session_para to keep
> > 64-bit alignment.
> > Remove irrelevant change by code format alignment.
> >
> > Also CC crypto gurus Herbert and linux-crypto@vger.kernel.org.
> >
> > Test with QEMU(patched by the v2 version), works fine.
> >
> > v1:
> > Introduce akcipher service, implement RSA algorithm, and a minor fix.
> >
> > zhenwei pi (4):
> > virtio_crypto: Introduce VIRTIO_CRYPTO_NOSPC
> > virtio-crypto: introduce akcipher service
> > virtio-crypto: implement RSA algorithm
> > virtio-crypto: rename skcipher algs
> >
> > drivers/crypto/virtio/Makefile | 3 +-
> > .../virtio/virtio_crypto_akcipher_algs.c | 585 ++++++++++++++++++
> > drivers/crypto/virtio/virtio_crypto_common.h | 7 +-
> > drivers/crypto/virtio/virtio_crypto_core.c | 6 +-
> > drivers/crypto/virtio/virtio_crypto_mgr.c | 15 +-
> > ...o_algs.c => virtio_crypto_skcipher_algs.c} | 4 +-
> > include/uapi/linux/virtio_crypto.h | 82 ++-
> > 7 files changed, 693 insertions(+), 9 deletions(-)
> > create mode 100644 drivers/crypto/virtio/virtio_crypto_akcipher_algs.c
> > rename drivers/crypto/virtio/{virtio_crypto_algs.c => virtio_crypto_skcipher_algs.c} (99%)
> >
>
> --
> zhenwei pi
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-03-07 9:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 3:39 [PATCH v3 0/4] Introduce akcipher service for virtio-crypto zhenwei pi
2022-03-02 3:39 ` [PATCH v3 1/4] virtio_crypto: Introduce VIRTIO_CRYPTO_NOSPC zhenwei pi
2022-03-02 3:39 ` [PATCH v3 2/4] virtio-crypto: introduce akcipher service zhenwei pi
2022-03-05 7:11 ` Gonglei (Arei) via Virtualization
2022-03-02 3:39 ` [PATCH v3 3/4] virtio-crypto: implement RSA algorithm zhenwei pi
2022-03-05 7:12 ` Gonglei (Arei) via Virtualization
2022-03-02 3:39 ` [PATCH v3 4/4] virtio-crypto: rename skcipher algs zhenwei pi
2022-03-05 7:12 ` Gonglei (Arei) via Virtualization
[not found] ` <Yh/WUSBesj/tRncT@gmail.com>
2022-03-03 1:59 ` Re: [PATCH v3 0/4] Introduce akcipher service for virtio-crypto zhenwei pi
2022-03-07 2:42 ` zhenwei pi
2022-03-07 9:05 ` Michael S. Tsirkin [this message]
2022-03-07 9:07 ` zhenwei pi
2022-04-04 15:39 ` Cornelia Huck
2022-04-05 5:20 ` Michael S. Tsirkin
2022-04-05 8:33 ` Cornelia Huck
2022-04-06 7:47 ` Michael S. Tsirkin
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=20220307040431-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@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 \
--cc=virtualization@lists.linux-foundation.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).