From: Herbert Xu <herbert@gondor.apana.org.au>
To: Pat Somaru <patso@likewhatevs.io>
Cc: Gonglei <arei.gonglei@huawei.com>,
"David S . Miller" <davem@davemloft.net>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>, "Tejun Heo" <tj@kernel.org>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
virtualization@lists.linux.dev, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: virtio: Convert from tasklet to BH workqueue
Date: Sat, 28 Feb 2026 17:43:37 +0900 [thread overview]
Message-ID: <aaKquVKecG8mCDXU@gondor.apana.org.au> (raw)
In-Reply-To: <20260207182001.2242836-1-patso@likewhatevs.io>
On Sat, Feb 07, 2026 at 01:20:01PM -0500, Pat Somaru wrote:
> The only generic interface to execute asynchronously in the BH context
> is tasklet; however, it's marked deprecated and has some design flaws
> such as the execution code accessing the tasklet item after the
> execution is complete which can lead to subtle use-after-free in certain
> usage scenarios and less-developed flush and cancel mechanisms.
>
> To replace tasklets, BH workqueue support was recently added. A BH
> workqueue behaves similarly to regular workqueues except that the queued
> work items are executed in the BH context.
>
> Convert virtio_crypto_core.c from tasklet to BH workqueue.
>
> Semantically, this is an equivalent conversion and there shouldn't be
> any user-visible behavior changes. The BH workqueue implementation uses
> the same softirq infrastructure, and performance-critical networking
> conversions have shown no measurable performance impact.
>
> Signed-off-by: Pat Somaru <patso@likewhatevs.io>
> ---
> Hi, I'm working on converting tasklet usages to the BH WQ API.
>
> The virtio-crypto driver uses a tasklet per data queue to process
> completed crypto operations in BH context. This converts that tasklet
> to use the BH workqueue infrastructure.
>
> This patch was tested by:
> - Building with allmodconfig: no new warnings (compared to v6.18)
> - Building with allyesconfig: no new warnings (compared to v6.18)
> - Booting defconfig kernel via vng and running `uname -a`:
> Linux virtme-ng 6.18.0-virtme #1 SMP PREEMPT_DYNAMIC 0 x86_64 GNU/Linux
>
> Maintainers can apply this directly to the crypto subsystem tree or ack
> it for the workqueue tree to carry.
>
> drivers/crypto/virtio/virtio_crypto_common.h | 3 ++-
> drivers/crypto/virtio/virtio_crypto_core.c | 11 +++++------
> 2 files changed, 7 insertions(+), 7 deletions(-)
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2026-02-28 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 18:20 [PATCH] crypto: virtio: Convert from tasklet to BH workqueue Pat Somaru
2026-02-28 8:43 ` Herbert Xu [this message]
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=aaKquVKecG8mCDXU@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=arei.gonglei@huawei.com \
--cc=davem@davemloft.net \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=patso@likewhatevs.io \
--cc=tj@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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