From: "Gonglei (Arei)" via <qemu-devel@nongnu.org>
To: zhenwei pi <pizhenwei@bytedance.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mst@redhat.com" <mst@redhat.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"helei.sig11@bytedance.com" <helei.sig11@bytedance.com>,
"berrange@redhat.com" <berrange@redhat.com>
Subject: RE: RE: [PATCH v8 1/1] crypto: Introduce RSA algorithm
Date: Tue, 31 May 2022 12:08:33 +0000 [thread overview]
Message-ID: <39f884dbc25d4b0cbec510ab090e6778@huawei.com> (raw)
In-Reply-To: <b2ee77ae-2044-32b4-20c5-43fa78e8213c@bytedance.com>
> -----Original Message-----
> From: zhenwei pi [mailto:pizhenwei@bytedance.com]
> Sent: Tuesday, May 31, 2022 9:48 AM
> To: Gonglei (Arei) <arei.gonglei@huawei.com>
> Cc: qemu-devel@nongnu.org; mst@redhat.com;
> virtualization@lists.linux-foundation.org; helei.sig11@bytedance.com;
> berrange@redhat.com
> Subject: Re: RE: [PATCH v8 1/1] crypto: Introduce RSA algorithm
>
> On 5/30/22 21:31, Gonglei (Arei) wrote:
> >
> >
> >> -----Original Message-----
> >> From: zhenwei pi [mailto:pizhenwei@bytedance.com]
> >> Sent: Friday, May 27, 2022 4:48 PM
> >> To: mst@redhat.com; Gonglei (Arei) <arei.gonglei@huawei.com>
> >> Cc: qemu-devel@nongnu.org; virtualization@lists.linux-foundation.org;
> >> helei.sig11@bytedance.com; berrange@redhat.com; zhenwei pi
> >> <pizhenwei@bytedance.com>
> >> Subject: [PATCH v8 1/1] crypto: Introduce RSA algorithm
> >>
> >>
> > Skip...
> >
> >> +static int64_t
> >> +virtio_crypto_create_asym_session(VirtIOCrypto *vcrypto,
> >> + struct virtio_crypto_akcipher_create_session_req
> >> *sess_req,
> >> + uint32_t queue_id, uint32_t opcode,
> >> + struct iovec *iov, unsigned int out_num) {
> >> + VirtIODevice *vdev = VIRTIO_DEVICE(vcrypto);
> >> + CryptoDevBackendSessionInfo info = {0};
> >> + CryptoDevBackendAsymSessionInfo *asym_info;
> >> + int64_t session_id;
> >> + int queue_index;
> >> + uint32_t algo, keytype, keylen;
> >> + g_autofree uint8_t *key = NULL;
> >> + Error *local_err = NULL;
> >> +
> >> + algo = ldl_le_p(&sess_req->para.algo);
> >> + keytype = ldl_le_p(&sess_req->para.keytype);
> >> + keylen = ldl_le_p(&sess_req->para.keylen);
> >> +
> >> + if ((keytype != VIRTIO_CRYPTO_AKCIPHER_KEY_TYPE_PUBLIC)
> >> + && (keytype !=
> VIRTIO_CRYPTO_AKCIPHER_KEY_TYPE_PRIVATE)) {
> >> + error_report("unsupported asym keytype: %d", keytype);
> >> + return -VIRTIO_CRYPTO_NOTSUPP;
> >> + }
> >> +
> >> + if (keylen) {
> >> + key = g_malloc(keylen);
> >> + if (iov_to_buf(iov, out_num, 0, key, keylen) != keylen) {
> >> + virtio_error(vdev, "virtio-crypto asym key incorrect");
> >> + return -EFAULT;
> >
> > Memory leak.
> >
> >> + }
> >> + iov_discard_front(&iov, &out_num, keylen);
> >> + }
> >> +
> >> + info.op_code = opcode;
> >> + asym_info = &info.u.asym_sess_info;
> >> + asym_info->algo = algo;
> >> + asym_info->keytype = keytype;
> >> + asym_info->keylen = keylen;
> >> + asym_info->key = key;
> >> + switch (asym_info->algo) {
> >> + case VIRTIO_CRYPTO_AKCIPHER_RSA:
> >> + asym_info->u.rsa.padding_algo =
> >> + ldl_le_p(&sess_req->para.u.rsa.padding_algo);
> >> + asym_info->u.rsa.hash_algo =
> >> + ldl_le_p(&sess_req->para.u.rsa.hash_algo);
> >> + break;
> >> +
> >> + /* TODO DSA&ECDSA handling */
> >> +
> >> + default:
> >> + return -VIRTIO_CRYPTO_ERR;
> >> + }
> >> +
> >> + queue_index = virtio_crypto_vq2q(queue_id);
> >> + session_id =
> >> + cryptodev_backend_create_session(vcrypto->cryptodev,
> >> &info,
> >> + queue_index, &local_err);
> >> + if (session_id < 0) {
> >> + if (local_err) {
> >> + error_report_err(local_err);
> >> + }
> >> + return -VIRTIO_CRYPTO_ERR;
> >> + }
> >> +
> >> + return session_id;
> >
> > Where to free the key at both normal and exceptional paths?
> >
>
> Hi, Lei
>
> The key is declared with g_autofree:
> g_autofree uint8_t *key = NULL;
>
OK. For the patch:
Reviewed-by: Gonglei <arei.gonglei@huawei.com>
Regards,
-Gonglei
next prev parent reply other threads:[~2022-05-31 12:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 8:47 Introduce akcipher service for virtio-crypto zhenwei pi
2022-05-27 8:47 ` [PATCH v8 1/1] crypto: Introduce RSA algorithm zhenwei pi
2022-05-30 13:31 ` Gonglei (Arei) via
2022-05-31 1:47 ` zhenwei pi
2022-05-31 12:08 ` Gonglei (Arei) via [this message]
2022-06-01 1:36 ` zhenwei pi
2022-06-09 0:57 ` PING: " zhenwei pi
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=39f884dbc25d4b0cbec510ab090e6778@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=helei.sig11@bytedance.com \
--cc=mst@redhat.com \
--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).