From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: Maxime Coquelin <mcoqueli@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Laurent Vivier <lvivier@redhat.com>,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
Cindy Lu <lulu@redhat.com>, Yongji Xie <xieyongji@bytedance.com>
Subject: Re: [PATCH 0/2] Fix lock errors in VDUSE suspend feature
Date: Thu, 11 Jun 2026 10:49:23 -0400 [thread overview]
Message-ID: <20260611104914-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20260611133806.198402-1-eperezma@redhat.com>
On Thu, Jun 11, 2026 at 03:38:04PM +0200, Eugenio Pérez wrote:
> Fix wrong ordering at taking semaphore after spinlock and convert the spinlock
> take and release into guards, so they are not lost after a return.
>
> This series goes on top of https://lore.kernel.org/lkml/20260610083452.477759-1-eperezma@redhat.com/
You mean
20260610-vduse_vq_kick-fix-guard-usage-v1-1-0ce02c08006e@kernel.org
actually
> ---
> It would be great if these can be squashed.
>
> Eugenio Pérez (2):
> vduse: fix not releasing taken semaphore in vduse_dev_queue_irq_work
> vduse: not take the device semaphore while holding vq spinlock
>
> drivers/vdpa/vdpa_user/vduse_dev.c | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
>
> --
> 2.54.0
next prev parent reply other threads:[~2026-06-11 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 13:38 [PATCH 0/2] Fix lock errors in VDUSE suspend feature Eugenio Pérez
2026-06-11 13:38 ` [PATCH 1/2] vduse: fix not releasing taken semaphore in vduse_dev_queue_irq_work Eugenio Pérez
2026-06-11 13:38 ` [PATCH 2/2] vduse: not take the device semaphore while holding vq spinlock Eugenio Pérez
2026-06-11 14:12 ` [PATCH 0/2] Fix lock errors in VDUSE suspend feature Michael S. Tsirkin
2026-06-11 14:14 ` Michael S. Tsirkin
2026-06-11 14:46 ` Michael S. Tsirkin
2026-06-11 14:49 ` Michael S. Tsirkin [this message]
2026-06-11 14:53 ` Michael S. Tsirkin
2026-06-11 16:33 ` Eugenio Perez Martin
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=20260611104914-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mcoqueli@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xieyongji@bytedance.com \
--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