From: Fang Xieyan <fangxy@xiaopeng.com>
To: "Michael S . Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowangio@gmail.com>,
"Eugenio Pérez" <eperezma@redhat.com>
Cc: Xie Yongji <xieyongji@bytedance.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
stable@vger.kernel.org, virtualization@lists.linux.dev,
kvm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] vringh: add regression test for cyclic indirect descriptor
Date: Tue, 22 Sep 2026 20:29:55 +0800 [thread overview]
Message-ID: <20260922122955.69433-3-fangxy@xiaopeng.com> (raw)
In-Reply-To: <20260922122955.69433-1-fangxy@xiaopeng.com>
Add a case to tools/virtio/vringh_test.c that builds a top-level
indirect descriptor whose NEXT points back at itself and checks that
vringh_getdesc_user() rejects it with -ELOOP.
Without the preceding fix, the walk re-enters the same top-level
descriptor without making forward progress: count stays flat, so the
traversal limit is never reached and -ELOOP is never returned. With the
fix, the top-level count advances on each re-entry and
vringh_getdesc_user() returns -ELOOP once the traversal limit is reached.
Use index 1 rather than 0 for the self-cycle, since returning from an
indirect table is only performed for a positive up_next value. A
self-cycle at index 0 would instead terminate the walk and would not
reproduce the bug.
Assisted-by: Hawkeye:GLM-5.3-flash
Assisted-by: Qoder:Qwen3.8-Max
Signed-off-by: Fang Xieyan <fangxy@xiaopeng.com>
---
tools/virtio/vringh_test.c | 41 ++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/tools/virtio/vringh_test.c b/tools/virtio/vringh_test.c
index 84961b9..2a5d7f7 100644
--- a/tools/virtio/vringh_test.c
+++ b/tools/virtio/vringh_test.c
@@ -458,6 +458,8 @@ int main(int argc, char *argv[])
int err;
unsigned i;
void *ret;
+ struct vring_desc *ind;
+ char *data;
bool (*getrange)(struct vringh *vrh, u64 addr, struct vringh_range *r);
bool fast_vringh = false, parallel = false;
@@ -755,6 +757,45 @@ int main(int argc, char *argv[])
vringh_iov_cleanup(&riov);
}
+ /*
+ * Regression test: a top-level indirect descriptor whose NEXT
+ * points back to itself must be rejected with -ELOOP instead of
+ * looping forever. Use index 1 rather than 0 so that returning
+ * from the indirect table re-enters the same top-level descriptor.
+ */
+ ind = __user_addr_max - USER_MEM/2;
+ data = __user_addr_max - USER_MEM/4;
+
+ /* Fresh ring and host state; resets last_avail_idx to 0. */
+ vring_init(&vrh.vring, RINGSIZE, __user_addr_min, ALIGN);
+ vringh_init_user(&vrh, vdev.features, RINGSIZE, true,
+ vrh.vring.desc, vrh.vring.avail, vrh.vring.used);
+
+ /* Single-entry indirect table pointing at valid data. */
+ ind[0].addr = (unsigned long)data;
+ ind[0].len = 1;
+ ind[0].flags = 0;
+
+ /* Top-level desc[1]: INDIRECT, and NEXT loops back to itself. */
+ vrh.vring.desc[1].addr = (unsigned long)ind;
+ vrh.vring.desc[1].len = sizeof(*ind);
+ vrh.vring.desc[1].flags = VRING_DESC_F_INDIRECT | VRING_DESC_F_NEXT;
+ vrh.vring.desc[1].next = 1;
+
+ /* Publish head 1 on the avail ring. */
+ vrh.vring.avail->ring[0] = 1;
+ vrh.vring.avail->idx = 1;
+
+ vringh_iov_init(&riov, host_riov, ARRAY_SIZE(host_riov));
+ vringh_iov_init(&wiov, host_wiov, ARRAY_SIZE(host_wiov));
+
+ err = vringh_getdesc_user(&vrh, &riov, &wiov, getrange, &head);
+ if (err != -ELOOP)
+ errx(1, "self-referential indirect: %i not -ELOOP", err);
+
+ vringh_iov_cleanup(&riov);
+ vringh_iov_cleanup(&wiov);
+
/* Don't leak memory... */
vring_del_virtqueue(vq);
free(__user_addr_min);
--
2.50.1
next prev parent reply other threads:[~2026-09-22 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 12:29 [PATCH 0/2] vringh: fix infinite loop on cyclic top-level indirect descriptor Fang Xieyan
2026-09-22 12:29 ` [PATCH 1/2] vringh: bound top-level re-entry into indirect tables Fang Xieyan
2026-09-22 12:39 ` sashiko-bot
2026-09-22 12:29 ` Fang Xieyan [this message]
2026-09-22 12:39 ` [PATCH 2/2] vringh: add regression test for cyclic indirect descriptor sashiko-bot
2026-09-26 6:43 ` Jason Wang
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=20260922122955.69433-3-fangxy@xiaopeng.com \
--to=fangxy@xiaopeng.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=stable@vger.kernel.org \
--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