From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Jens Freimann" <jfreiman@redhat.com>,
"Victor Kaplansky" <victork@redhat.com>,
"Yuanhan Liu" <yuanhan.liu@linux.intel.com>
Subject: [Qemu-devel] [PULL 1/3] vhost-user-bridge: fix iov_restore_front() warning
Date: Thu, 8 Jun 2017 22:36:24 +0300 [thread overview]
Message-ID: <1496950567-26343-2-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1496950567-26343-1-git-send-email-mst@redhat.com>
From: Marc-André Lureau <marcandre.lureau@redhat.com>
CC tests/vhost-user-bridge.o
/home/dgilbert/git/qemu-world3/tests/vhost-user-bridge.c:228:23: warning: variables 'front' and 'iov' used in loop condition not modified in loop body [-Wfor-loop-analysis]
for (cur = front; front != iov; cur++) {
^~~~~ ~~~
1 warning generated.
Fix the loop, document the function, and fix some related assert().
In practice, the loop bug was harmless because the front sg buffer is
enough to discard/restore the header size.
Reported-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Tested-by: Jens Freimann <jfreiman@redhat.com>
---
tests/vhost-user-bridge.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/tests/vhost-user-bridge.c b/tests/vhost-user-bridge.c
index 8618c20..1e5b5ca 100644
--- a/tests/vhost-user-bridge.c
+++ b/tests/vhost-user-bridge.c
@@ -220,12 +220,18 @@ vubr_handle_tx(VuDev *dev, int qidx)
free(elem);
}
+
+/* this function reverse the effect of iov_discard_front() it must be
+ * called with 'front' being the original struct iovec and 'bytes'
+ * being the number of bytes you shaved off
+ */
static void
iov_restore_front(struct iovec *front, struct iovec *iov, size_t bytes)
{
struct iovec *cur;
- for (cur = front; front != iov; cur++) {
+ for (cur = front; cur != iov; cur++) {
+ assert(bytes >= cur->iov_len);
bytes -= cur->iov_len;
}
@@ -302,7 +308,8 @@ vubr_backend_recv_cb(int sock, void *ctx)
}
iov_from_buf(sg, elem->in_num, 0, &hdr, sizeof hdr);
total += hdrlen;
- assert(iov_discard_front(&sg, &num, hdrlen) == hdrlen);
+ ret = iov_discard_front(&sg, &num, hdrlen);
+ assert(ret == hdrlen);
}
struct msghdr msg = {
--
MST
next prev parent reply other threads:[~2017-06-08 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 19:36 [Qemu-devel] [PULL 0/3] pc, pci, vhost: fixes Michael S. Tsirkin
2017-06-08 19:36 ` Michael S. Tsirkin [this message]
2017-06-08 19:36 ` [Qemu-devel] [PULL 2/3] nvdimm acpi: fix region format interface code Michael S. Tsirkin
2017-06-08 19:36 ` [Qemu-devel] [PULL 3/3] hw/pcie: fix the generic pcie root port to support migration Michael S. Tsirkin
2017-06-13 10:55 ` [Qemu-devel] [PULL 0/3] pc, pci, vhost: fixes Peter Maydell
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=1496950567-26343-2-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jfreiman@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=victork@redhat.com \
--cc=yuanhan.liu@linux.intel.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).