qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
	Fam Zheng <famz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [RFC v2 6/9] virtio: use unsigned int for virtqueue_get_avail_bytes() index
Date: Tue, 29 Mar 2016 17:12:58 +0100	[thread overview]
Message-ID: <1459267981-23408-7-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1459267981-23408-1-git-send-email-stefanha@redhat.com>

The virtio code uses int, unsigned int, and uint16_t for virtqueue
indices.  The uint16_t is used for the low-level descriptor layout in
virtio_ring.h while code that isn't concerned with descriptor layout can
use unsigned int.

Use of int is problematic because it can result in signed/unsigned
comparison and incompatible int*/unsigned int* pointer types.

Make the virtqueue_get_avail_bytes() 'i' variable unsigned int.  This
eliminates the need to introduce casts and modify code further in the
patches that follow.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 hw/virtio/virtio.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
index a7459c2..07ce02b 100644
--- a/hw/virtio/virtio.c
+++ b/hw/virtio/virtio.c
@@ -389,7 +389,7 @@ void virtqueue_get_avail_bytes(VirtQueue *vq, unsigned int *in_bytes,
         unsigned int max, num_bufs, indirect = 0;
         VRingDesc desc;
         hwaddr desc_pa;
-        int i;
+        unsigned int i;
 
         max = vq->vring.num;
         num_bufs = total_bufs;
-- 
2.5.5

  parent reply	other threads:[~2016-03-29 16:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 16:12 [Qemu-devel] [RFC v2 0/9] virtio: avoid exit() when device enters invalid states Stefan Hajnoczi
2016-03-29 16:12 ` [Qemu-devel] [RFC v2 1/9] virtio: fix stray tab character Stefan Hajnoczi
2016-04-07 14:50   ` Markus Armbruster
2016-04-08  9:06     ` Stefan Hajnoczi
2016-04-08 11:10       ` Markus Armbruster
2016-03-29 16:12 ` [Qemu-devel] [RFC v2 2/9] include: update virtio_config.h Linux header Stefan Hajnoczi
2016-03-29 16:12 ` [Qemu-devel] [RFC v2 3/9] virtio: stop virtqueue processing if device is broken Stefan Hajnoczi
2016-03-29 16:58   ` Cornelia Huck
2016-03-30 12:19     ` Stefan Hajnoczi
2016-03-30 12:21     ` Stefan Hajnoczi
2016-03-29 16:12 ` [Qemu-devel] [RFC v2 4/9] virtio: handle virtqueue_map_desc() errors Stefan Hajnoczi
2016-03-29 16:12 ` [Qemu-devel] [RFC v2 5/9] virtio: handle virtqueue_get_avail_bytes() errors Stefan Hajnoczi
2016-03-29 16:12 ` Stefan Hajnoczi [this message]
2016-03-29 16:12 ` [Qemu-devel] [RFC v2 7/9] virtio: handle virtqueue_read_next_desc() errors Stefan Hajnoczi
2016-03-29 16:13 ` [Qemu-devel] [RFC v2 8/9] virtio: handle virtqueue_num_heads() errors Stefan Hajnoczi
2016-03-29 16:13 ` [Qemu-devel] [RFC v2 9/9] virtio: handle virtqueue_get_head() errors 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=1459267981-23408-7-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=famz@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).