]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
crypto: virtio - Add spinlock protection with virtqueue notification
authorBibo Mao <maobibo@loongson.cn>
Tue, 13 Jan 2026 03:05:54 +0000 (11:05 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 16 Feb 2026 09:19:44 +0000 (10:19 +0100)
commite69a7b0a71b6561b3b6459f1fded8d589f2e8ac2
tree3598c5830ff0e0dde1fd58f89efa6db4328deba8
parent2ed27b5a1174351148c3adbfc0cd86d54072ba2e
crypto: virtio - Add spinlock protection with virtqueue notification

commit b505047ffc8057555900d2d3a005d033e6967382 upstream.

When VM boots with one virtio-crypto PCI device and builtin backend,
run openssl benchmark command with multiple processes, such as
  openssl speed -evp aes-128-cbc -engine afalg  -seconds 10 -multi 32

openssl processes will hangup and there is error reported like this:
 virtio_crypto virtio0: dataq.0:id 3 is not a head!

It seems that the data virtqueue need protection when it is handled
for virtio done notification. If the spinlock protection is added
in virtcrypto_done_task(), openssl benchmark with multiple processes
works well.

Fixes: fed93fb62e05 ("crypto: virtio - Handle dataq logic with tasklet")
Cc: stable@vger.kernel.org
Signed-off-by: Bibo Mao <maobibo@loongson.cn>
Acked-by: Jason Wang <jasowang@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/crypto/virtio/virtio_crypto_core.c