From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
axboe@kernel.dk, virtualization@lists.linux.dev,
linux-block@vger.kernel.org, stable@vger.kernel.org,
lirongqing@baidu.com, kch@nvidia.com, xuanzhuo@linux.alibaba.com,
pbonzini@redhat.com, jasowang@redhat.com,
alok.a.tiwari@oracle.com, Max Gurtovoy <mgurtovoy@nvidia.com>,
Israel Rukshin <israelr@nvidia.com>
Subject: Re: [PATCH v5] virtio_blk: Fix disk deletion hang on device surprise removal
Date: Wed, 25 Jun 2025 08:39:07 -0400 [thread overview]
Message-ID: <20250625083746-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250624185622.GB5519@fedora>
On Tue, Jun 24, 2025 at 02:56:22PM -0400, Stefan Hajnoczi wrote:
> On Mon, Jun 02, 2025 at 02:44:33AM +0000, Parav Pandit wrote:
> > When the PCI device is surprise removed, requests may not complete
> > the device as the VQ is marked as broken. Due to this, the disk
> > deletion hangs.
>
> There are loops in the core virtio driver code that expect device
> register reads to eventually return 0:
> drivers/virtio/virtio_pci_modern.c:vp_reset()
> drivers/virtio/virtio_pci_modern_dev.c:vp_modern_set_queue_reset()
>
> Is there a hang if these loops are hit when a device has been surprise
> removed? I'm trying to understand whether surprise removal is fully
> supported or whether this patch is one step in that direction.
>
> Apart from that, I'm happy with the virtio_blk.c aspects of the patch:
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Is this as simple as this?
-->
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
diff --git a/drivers/virtio/virtio_pci_modern.c b/drivers/virtio/virtio_pci_modern.c
index 7182f43ed055..df983fa9046a 100644
--- a/drivers/virtio/virtio_pci_modern.c
+++ b/drivers/virtio/virtio_pci_modern.c
@@ -555,8 +555,12 @@ static void vp_reset(struct virtio_device *vdev)
* This will flush out the status write, and flush in device writes,
* including MSI-X interrupts, if any.
*/
- while (vp_modern_get_status(mdev))
+ while (vp_modern_get_status(mdev)) {
+ /* If device is removed meanwhile, it will never respond. */
+ if (!pci_device_is_present(vp_dev->pci_dev))
+ break;
msleep(1);
+ }
vp_modern_avq_cleanup(vdev);
diff --git a/drivers/virtio/virtio_pci_modern_dev.c b/drivers/virtio/virtio_pci_modern_dev.c
index 0d3dbfaf4b23..7177ce0d63be 100644
--- a/drivers/virtio/virtio_pci_modern_dev.c
+++ b/drivers/virtio/virtio_pci_modern_dev.c
@@ -523,11 +523,19 @@ void vp_modern_set_queue_reset(struct virtio_pci_modern_device *mdev, u16 index)
vp_iowrite16(index, &cfg->cfg.queue_select);
vp_iowrite16(1, &cfg->queue_reset);
- while (vp_ioread16(&cfg->queue_reset))
+ while (vp_ioread16(&cfg->queue_reset)) {
+ /* If device is removed meanwhile, it will never respond. */
+ if (!pci_device_is_present(vp_dev->pci_dev))
+ break;
msleep(1);
+ }
- while (vp_ioread16(&cfg->cfg.queue_enable))
+ while (vp_ioread16(&cfg->cfg.queue_enable)) {
+ /* If device is removed meanwhile, it will never respond. */
+ if (!pci_device_is_present(vp_dev->pci_dev))
+ break;
msleep(1);
+ }
}
EXPORT_SYMBOL_GPL(vp_modern_set_queue_reset);
next prev parent reply other threads:[~2025-06-25 12:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 2:44 [PATCH v5] virtio_blk: Fix disk deletion hang on device surprise removal Parav Pandit
2025-06-02 11:46 ` ALOK TIWARI
2025-06-18 9:29 ` Parav Pandit
2025-06-24 18:56 ` Stefan Hajnoczi
2025-06-24 19:01 ` Parav Pandit
2025-06-24 19:06 ` Michael S. Tsirkin
2025-06-24 19:11 ` Parav Pandit
2025-06-24 19:54 ` Michael S. Tsirkin
2025-06-25 2:55 ` Parav Pandit
2025-06-25 11:04 ` Michael S. Tsirkin
2025-06-25 11:08 ` Parav Pandit
2025-06-25 11:44 ` Michael S. Tsirkin
2025-06-25 19:08 ` Parav Pandit
2025-06-25 19:22 ` Michael S. Tsirkin
2025-06-26 3:26 ` Parav Pandit
2025-06-26 6:04 ` Michael S. Tsirkin
2025-06-26 6:29 ` Parav Pandit
2025-06-26 6:33 ` Michael S. Tsirkin
2025-06-26 9:19 ` Parav Pandit
2025-06-27 12:21 ` Michael S. Tsirkin
2025-06-27 14:00 ` Keith Busch
2025-06-24 19:06 ` Michael S. Tsirkin
2025-06-25 12:39 ` Michael S. Tsirkin [this message]
2025-06-25 19:01 ` Parav Pandit
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=20250625083746-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alok.a.tiwari@oracle.com \
--cc=axboe@kernel.dk \
--cc=israelr@nvidia.com \
--cc=jasowang@redhat.com \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mgurtovoy@nvidia.com \
--cc=parav@nvidia.com \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--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