From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Rusty Russell <rusty@rustcorp.com.au>
Subject: [Qemu-devel] [PATCH] virtio: move sanity checks to ifdef DEBUG
Date: Wed, 18 Mar 2015 12:42:46 +0100 [thread overview]
Message-ID: <1426678962-27545-1-git-send-email-mst@redhat.com> (raw)
All that happens when virtqueue_fill is invoked incorrectly is that we
corrupt guest memory, so this check is not a security measure.
Move the check to ifdef DEBUG to make sure we don't introduce new
crashes close to release.
Array scans aren't free either, so it's a good idea from performance
point of view, too.
Cc: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
hw/virtio/virtio.c | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
index 27429c2..37fb2ee 100644
--- a/hw/virtio/virtio.c
+++ b/hw/virtio/virtio.c
@@ -243,15 +243,22 @@ int virtio_queue_empty(VirtQueue *vq)
void virtqueue_fill(VirtQueue *vq, const VirtQueueElement *elem,
unsigned int len_written, unsigned int idx)
{
- unsigned int offset, tot_wlen;
+ unsigned int offset;
int i;
trace_virtqueue_fill(vq, elem, len_written, idx);
- for (tot_wlen = i = 0; i < elem->in_num; i++) {
- tot_wlen += elem->in_sg[i].iov_len;
+#ifdef DEBUG_VIRTIO
+ {
+ /* Check that len_written is <= the writable length. */
+ unsigned int tot_wlen;
+
+ for (tot_wlen = i = 0; i < elem->in_num; i++) {
+ tot_wlen += elem->in_sg[i].iov_len;
+ }
+ assert(len_written <= tot_wlen);
}
- assert(len_written <= tot_wlen);
+#endif
offset = 0;
for (i = 0; i < elem->in_num; i++) {
--
MST
next reply other threads:[~2015-03-18 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 11:42 Michael S. Tsirkin [this message]
2015-03-20 8:12 ` [Qemu-devel] [PATCH] virtio: move sanity checks to ifdef DEBUG Cornelia Huck
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=1426678962-27545-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).