From: Stefano Garzarella <sgarzare@redhat.com>
To: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
mst@redhat.com, stefanha@redhat.com, jasowangio@gmail.com,
eperezma@redhat.com
Subject: Re: [PATCH] vhost: clear vq->worker under vq->mutex when freeing workers
Date: Thu, 6 Aug 2026 15:35:27 +0200 [thread overview]
Message-ID: <anSMBpQJ8x-vXYy2@sgarzare-redhat> (raw)
In-Reply-To: <20260723153310.745855-1-andrey.drobyshev@virtuozzo.com>
On Thu, Jul 23, 2026 at 06:33:10PM +0300, Andrey Drobyshev wrote:
>Every other update of vq->worker is done under vq->mutex - the worker
>attach/swap ioctls and vhost_worker_killed(). vhost_workers_free() is
>the sole exception: it clears vq->worker without holding the lock.
mmm, vhost_dev_cleanup() updates vq->worker without the mutex too IIUC.
>
>The effect is harmless in practice, as this only happens while the
>owning process (and thus the whole device) is dying, but the lockless
>write is inconsistent with the rest of the code. Clear vq->worker under
>vq->mutex, like everyone else, so that all writers of vq->worker follow
>the same locking rule.
>
>This issue was found by Sashiko AI review.
Can you share a link to the review?
I don't know if it's common or not, but having the link in the commit or
after --- will help the reviewers.
>
>Signed-off-by: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
>---
> drivers/vhost/vhost.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
>index 4c525b3e16ea..dbb6cb5eccea 100644
>--- a/drivers/vhost/vhost.c
>+++ b/drivers/vhost/vhost.c
>@@ -722,13 +722,19 @@ static void vhost_worker_destroy(struct vhost_dev *dev,
> static void vhost_workers_free(struct vhost_dev *dev)
> {
> struct vhost_worker *worker;
>+ struct vhost_virtqueue *vq;
> unsigned long i;
>
> if (!dev->use_worker)
> return;
>
>- for (i = 0; i < dev->nvqs; i++)
>- rcu_assign_pointer(dev->vqs[i]->worker, NULL);
>+ for (i = 0; i < dev->nvqs; i++) {
>+ vq = dev->vqs[i];
>+
>+ mutex_lock(&vq->mutex);
>+ rcu_assign_pointer(vq->worker, NULL);
>+ mutex_unlock(&vq->mutex);
>+ }
Pre-existing, but IIUC vhost_workers_free() is called only by
vhost_dev_cleanup() at the bottom, after a loop calls vhost_vq_reset()
on each virtqueue (without the mutex) where we already set `vq->worker`
to NULL, so IMO at this point it's already NULL, no?
Thanks,
Stefano
> /*
> * Free the default worker we created and cleanup workers userspace
> * created but couldn't clean up (it forgot or crashed).
>--
>2.47.1
>
next prev parent reply other threads:[~2026-08-06 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 15:33 [PATCH] vhost: clear vq->worker under vq->mutex when freeing workers Andrey Drobyshev
2026-08-06 13:35 ` Stefano Garzarella [this message]
2026-08-06 13:53 ` Sean Christopherson
2026-08-06 14:12 ` Stefano Garzarella
2026-08-06 14:40 ` Stefano Garzarella
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=anSMBpQJ8x-vXYy2@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=andrey.drobyshev@virtuozzo.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
/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