From: "Longpeng(Mike)" <longpeng2@huawei.com>
To: stefanha@redhat.com, lvivier@redhat.com, eblake@redhat.com,
peter.maydell@linaro.org, groug@kaod.org
Cc: arei.gonglei@huawei.com, qemu-devel@nongnu.org,
"Longpeng(Mike)" <longpeng2@huawei.com>
Subject: [Qemu-devel] [PATCH v2] qtest: virtio: zeroed last vring_desc after allocate
Date: Tue, 17 Jan 2017 10:59:24 +0800 [thread overview]
Message-ID: <1484621964-187372-1-git-send-email-longpeng2@huawei.com> (raw)
As qvring_indirect_desc_setup() wouldn't initialize last vring_desc,
so it's filled with dirty data, this might cause virtio backend broken.
For example, the last bit of this vring_desc's flags might be 1, so
virtqueue_read_next_desc() would report "Desc next is ***".
Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>
---
Changes since v1:
- use writel() for @len as it's 32 bits long. [Stefan]
---
tests/libqos/virtio.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/tests/libqos/virtio.c b/tests/libqos/virtio.c
index ec30cb9..02e6a43 100644
--- a/tests/libqos/virtio.c
+++ b/tests/libqos/virtio.c
@@ -171,12 +171,20 @@ QVRingIndirectDesc *qvring_indirect_desc_setup(QVirtioDevice *d,
for (i = 0; i < elem - 1; ++i) {
/* indirect->desc[i].addr */
writeq(indirect->desc + (16 * i), 0);
+ /* indirect->desc[i].len */
+ writel(indirect->desc + (16 * i) + 8, 0);
/* indirect->desc[i].flags */
writew(indirect->desc + (16 * i) + 12, VRING_DESC_F_NEXT);
/* indirect->desc[i].next */
writew(indirect->desc + (16 * i) + 14, i + 1);
}
+ /* zeroed last element */
+ writeq(indirect->desc + (16 * i), 0); /* addr */
+ writel(indirect->desc + (16 * i) + 8, 0); /* len */
+ writew(indirect->desc + (16 * i) + 12, 0); /* flags */
+ writew(indirect->desc + (16 * i) + 14, 0); /* next */
+
return indirect;
}
--
1.8.3.1
next reply other threads:[~2017-01-17 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 2:59 Longpeng(Mike) [this message]
2017-01-17 10:55 ` [Qemu-devel] [PATCH v2] qtest: virtio: zeroed last vring_desc after allocate Stefan Hajnoczi
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=1484621964-187372-1-git-send-email-longpeng2@huawei.com \
--to=longpeng2@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=eblake@redhat.com \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).