From: Amit Shah <amit.shah@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu list <qemu-devel@nongnu.org>,
Amit Shah <amit.shah@redhat.com>, Avi Kivity <avi@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCH v5 13/17] virtio-serial: Handle scatter-gather buffers for control messages
Date: Wed, 14 Apr 2010 10:58:33 +0530 [thread overview]
Message-ID: <1271222917-7803-14-git-send-email-amit.shah@redhat.com> (raw)
In-Reply-To: <1271222917-7803-13-git-send-email-amit.shah@redhat.com>
Current control messages are small enough to not be split into multiple
buffers but we could run into such a situation in the future or a
malicious guest could cause such a situation.
So handle the entire iov request for control messages.
Also ensure the size of the control request is >= what we expect
otherwise we risk accessing memory that we don't own.
Signed-off-by: Amit Shah <amit.shah@redhat.com>
CC: Avi Kivity <avi@redhat.com>
Reported-by: Avi Kivity <avi@redhat.com>
---
hw/virtio-serial-bus.c | 31 ++++++++++++++++++++++++++++---
1 files changed, 28 insertions(+), 3 deletions(-)
diff --git a/hw/virtio-serial-bus.c b/hw/virtio-serial-bus.c
index a72b6b5..b8410c3 100644
--- a/hw/virtio-serial-bus.c
+++ b/hw/virtio-serial-bus.c
@@ -204,7 +204,7 @@ size_t virtio_serial_guest_ready(VirtIOSerialPort *port)
}
/* Guest wants to notify us of some event */
-static void handle_control_message(VirtIOSerial *vser, void *buf)
+static void handle_control_message(VirtIOSerial *vser, void *buf, size_t len)
{
struct VirtIOSerialPort *port;
struct virtio_console_control cpkt, *gcpkt;
@@ -213,6 +213,11 @@ static void handle_control_message(VirtIOSerial *vser, void *buf)
gcpkt = buf;
+ if (len < sizeof(cpkt)) {
+ /* The guest sent an invalid control packet */
+ return;
+ }
+
cpkt.event = lduw_p(&gcpkt->event);
cpkt.value = lduw_p(&gcpkt->value);
@@ -306,13 +311,33 @@ static void control_out(VirtIODevice *vdev, VirtQueue *vq)
{
VirtQueueElement elem;
VirtIOSerial *vser;
+ uint8_t *buf;
+ size_t len;
vser = DO_UPCAST(VirtIOSerial, vdev, vdev);
+ len = 0;
+ buf = NULL;
while (virtqueue_pop(vq, &elem)) {
- handle_control_message(vser, elem.out_sg[0].iov_base);
- virtqueue_push(vq, &elem, elem.out_sg[0].iov_len);
+ size_t cur_len, copied;
+
+ cur_len = iov_size(elem.out_sg, elem.out_num);
+ /*
+ * Allocate a new buf only if we didn't have one previously or
+ * if the size of the buf differs
+ */
+ if (cur_len > len) {
+ qemu_free(buf);
+
+ buf = qemu_malloc(cur_len);
+ len = cur_len;
+ }
+ copied = iov_to_buf(elem.out_sg, elem.out_num, buf, 0, len);
+
+ handle_control_message(vser, buf, copied);
+ virtqueue_push(vq, &elem, copied);
}
+ qemu_free(buf);
virtio_notify(vdev, vq);
}
--
1.6.2.5
next prev parent reply other threads:[~2010-04-14 5:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 5:28 [Qemu-devel] [PATCH v5 00/17] virtio-serial fixes, new abi for port discovery, flow control Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 01/17] virtio-serial: save/load: Ensure target has enough ports Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 02/17] virtio-serial: save/load: Ensure nr_ports on src and dest are same Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 03/17] virtio-serial: save/load: Ensure we have hot-plugged ports instantiated Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 04/17] virtio-serial: save/load: Send target host connection status if different Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 05/17] virtio-serial: Use control messages to notify guest of new ports Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 06/17] virtio-serial: whitespace: match surrounding code Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 07/17] virtio-serial: Remove redundant check for 0-sized write request Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 08/17] virtio-serial: Update copyright year to 2010 Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 09/17] virtio-serial: Propagate errors in initialising ports / devices in guest Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 10/17] virtio-serial: Send out guest data to ports only if port is opened Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 11/17] iov: Introduce a new file for helpers around iovs, add iov_from_buf() Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 12/17] iov: Add iov_to_buf and iov_size helpers Amit Shah
2010-04-14 5:28 ` Amit Shah [this message]
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 14/17] virtio-serial: Handle scatter/gather input from the guest Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 15/17] virtio-serial: Apps should consume all data that guest sends out / Fix virtio api abuse Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 16/17] virtio-serial: Discard data that guest sends us when ports aren't connected Amit Shah
2010-04-14 5:28 ` [Qemu-devel] [PATCH v5 17/17] virtio-serial: Implement flow control for individual ports Amit Shah
2010-04-14 7:48 ` [Qemu-devel] Re: [PATCH v5 00/17] virtio-serial fixes, new abi for port discovery, flow control Juan Quintela
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=1271222917-7803-14-git-send-email-amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).