From: "Michael S. Tsirkin" <mst@redhat.com>
To: Bibo Mao <maobibo@loongson.cn>
Cc: Gonglei <arei.gonglei@huawei.com>,
Jason Wang <jasowang@redhat.com>,
Eric Biggers <ebiggers@kernel.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v4 0/9] crypto: virtio: Some bugfix and enhancement
Date: Fri, 26 Dec 2025 09:45:29 -0500 [thread overview]
Message-ID: <20251226094413-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20251218034846.948860-1-maobibo@loongson.cn>
On Thu, Dec 18, 2025 at 11:48:37AM +0800, Bibo Mao wrote:
> There is problem when multiple processes add encrypt/decrypt requests
> with virtio crypto device and spinlock is missing with command response
> handling. Also there is duplicated virtqueue_kick() without lock hold.
>
> Here these two issues are fixed and the others are code clean up, such as
> use common APIs for block size and iv size etc.
series:
Acked-by: Michael S. Tsirkin <mst@redhat.com>
but you did not CC maintainers, you really should if you want this
applied.
> ---
> v3 ... v4:
> 1. Remove patch 10 which adds ECB AES algo, since application and qemu
> backend emulation is not ready for ECB AES algo.
> 2. Add Cc stable tag with patch 2 which removes duplicated
> virtqueue_kick() without lock hold.
>
> v2 ... v3:
> 1. Remove NULL checking with req_data where kfree() is called, since
> NULL pointer is workable with kfree() API.
> 2. In patch 7 and patch 8, req_data and IV buffer which are preallocated
> are sensitive data, memzero_explicit() is used even on error path
> handling.
> 3. Remove duplicated virtqueue_kick() in new patch 2, since it is
> already called in previous __virtio_crypto_skcipher_do_req().
>
> v1 ... v2:
> 1. Add Fixes tag with patch 1.
> 2. Add new patch 2 - patch 9 to add ecb aes algo support.
> ---
> Bibo Mao (9):
> crypto: virtio: Add spinlock protection with virtqueue notification
> crypto: virtio: Remove duplicated virtqueue_kick in
> virtio_crypto_skcipher_crypt_req
> crypto: virtio: Replace package id with numa node id
> crypto: virtio: Add algo pointer in virtio_crypto_skcipher_ctx
> crypto: virtio: Use generic API aes_check_keylen()
> crypto: virtio: Remove AES specified marcro AES_BLOCK_SIZE
> crypto: virtio: Add req_data with structure virtio_crypto_sym_request
> crypto: virtio: Add IV buffer in structure virtio_crypto_sym_request
> crypto: virtio: Add skcipher support without IV
>
> drivers/crypto/virtio/virtio_crypto_common.h | 2 +-
> drivers/crypto/virtio/virtio_crypto_core.c | 5 +
> .../virtio/virtio_crypto_skcipher_algs.c | 113 +++++++++---------
> 3 files changed, 62 insertions(+), 58 deletions(-)
>
>
> base-commit: ea1013c1539270e372fc99854bc6e4d94eaeff66
> --
> 2.39.3
next prev parent reply other threads:[~2025-12-26 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 3:48 [PATCH v4 0/9] crypto: virtio: Some bugfix and enhancement Bibo Mao
2025-12-18 3:48 ` [PATCH v4 1/9] crypto: virtio: Add spinlock protection with virtqueue notification Bibo Mao
2025-12-18 3:48 ` [PATCH v4 2/9] crypto: virtio: Remove duplicated virtqueue_kick in virtio_crypto_skcipher_crypt_req Bibo Mao
2025-12-18 3:52 ` Jason Wang
2025-12-18 3:48 ` [PATCH v4 3/9] crypto: virtio: Replace package id with numa node id Bibo Mao
2025-12-18 3:48 ` [PATCH v4 4/9] crypto: virtio: Add algo pointer in virtio_crypto_skcipher_ctx Bibo Mao
2025-12-18 3:48 ` [PATCH v4 5/9] crypto: virtio: Use generic API aes_check_keylen() Bibo Mao
2025-12-18 3:48 ` [PATCH v4 6/9] crypto: virtio: Remove AES specified marcro AES_BLOCK_SIZE Bibo Mao
2025-12-18 3:48 ` [PATCH v4 7/9] crypto: virtio: Add req_data with structure virtio_crypto_sym_request Bibo Mao
2025-12-18 3:48 ` [PATCH v4 8/9] crypto: virtio: Add IV buffer in " Bibo Mao
2025-12-18 3:48 ` [PATCH v4 9/9] crypto: virtio: Add skcipher support without IV Bibo Mao
2025-12-26 14:45 ` Michael S. Tsirkin [this message]
2025-12-29 2:09 ` [PATCH v4 0/9] crypto: virtio: Some bugfix and enhancement Bibo Mao
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=20251226094413-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=ebiggers@kernel.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maobibo@loongson.cn \
/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