From: Abhin Parekadan Jose <abhinjoses@gmail.com>
To: mst@redhat.com, jasowangio@gmail.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com
Cc: virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
Abhin Parekadan Jose <abhinjoses@gmail.com>
Subject: [PATCH 0/2] virtio_pci_modern: fix vp_reset() hang on unresponsive device
Date: Sun, 2 Aug 2026 17:40:57 +0000 [thread overview]
Message-ID: <20260802174059.4082-1-abhinjoses@gmail.com> (raw)
While investigating a syzbot report of a WARN_ON_ONCE firing in
virtio_dev_remove() [1], I found a related but more serious issue:
vp_reset() in the modern virtio-pci transport can hang indefinitely
if PCI_COMMAND memory-space decode is disabled while the device is
bound (e.g. surprise removal, hardware fault, or -- as reproduced
here -- a direct write to the PCI_COMMAND register). The status
register poll loop has no way to distinguish "device still resetting"
from "device unreachable," so it never terminates.
Patch 1 adds a VIRTIO_STATUS_ERROR() check that recognizes an
all-ones status read as invalid (per spec, bits 4-5 are reserved and
can never legitimately be set) and warns once at the point the bad
read actually happens.
Patch 2 uses that check to break out of vp_reset()'s poll loop
instead of spinning forever.
Reproduced on a modern-transport virtio-blk-pci device:
# printf '\x00\x00' | dd of=/sys/bus/pci/devices/0000:01:00.0/config \
bs=1 seek=4 count=2 conv=notrunc
# echo 1 > /sys/bus/pci/devices/0000:01:00.0/remove
The second command hangs indefinitely without this series; gdb
confirms the CPU is stuck in vp_reset()'s status-polling loop, with
vp_modern_get_status() consistently returning 0xff.
[1] https://syzbot.org/bug?extid=a1c8effc62c569d4bd25
Abhin Parekadan Jose (2):
virtio_pci_modern_dev: warn once on invalid status
virtio_pci_modern: avoid infinite loop in vp_reset() on invalid status
drivers/virtio/virtio_pci_modern.c | 6 +++++-
drivers/virtio/virtio_pci_modern_dev.c | 8 +++++++-
include/uapi/linux/virtio_config.h | 16 ++++++++++++++++
3 files changed, 28 insertions(+), 2 deletions(-)
--
2.51.1
next reply other threads:[~2026-08-02 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 17:40 Abhin Parekadan Jose [this message]
2026-08-02 17:40 ` [PATCH 1/2] virtio_pci_modern_dev: warn once on invalid status Abhin Parekadan Jose
2026-08-02 18:10 ` Michael S. Tsirkin
2026-08-02 17:40 ` [PATCH 2/2] virtio_pci_modern: avoid infinite loop in vp_reset() " Abhin Parekadan Jose
2026-08-02 18:06 ` Michael S. Tsirkin
2026-08-02 17:47 ` [PATCH 0/2] virtio_pci_modern: fix vp_reset() hang on unresponsive device Michael S. Tsirkin
2026-08-02 18:28 ` Abhin Parekadan Jose
2026-08-02 19:08 ` Michael S. Tsirkin
2026-08-02 19:48 ` Abhin Parekadan Jose
2026-08-02 19:54 ` Michael S. Tsirkin
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=20260802174059.4082-1-abhinjoses@gmail.com \
--to=abhinjoses@gmail.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@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