From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Greg Kurz <groug@kaod.org>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH v4 2/4] virtio-9p: message header is 7-byte long
Date: Fri, 23 Jun 2017 08:45:16 +0200 [thread overview]
Message-ID: <149820031604.7187.14987200901766883821.stgit@bahia.lan> (raw)
In-Reply-To: <149820029273.7187.14110849422638329192.stgit@bahia.lan>
The 9p spec at http://man.cat-v.org/plan_9/5/intro reads:
"Each 9P message begins with a four-byte size field specify-
ing the length in bytes of the complete message including
the four bytes of the size field itself. The next byte is
the message type, one of the constants in the enumeration in
the include file <fcall.h>. The next two bytes are an iden-
tifying tag, described below."
ie, each message starts with a 7-byte long header.
The core 9P code already assumes this pretty much everywhere. This patch
does the following:
- makes the assumption explicit in the common 9p.h header, since it isn't
related to the transport
- open codes the header size in handle_9p_output() and hardens the sanity
check on the space needed for the reply message
Signed-off-by: Greg Kurz <groug@kaod.org>
---
hw/9pfs/9p.h | 5 +++++
hw/9pfs/virtio-9p-device.c | 8 +++-----
2 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/hw/9pfs/9p.h b/hw/9pfs/9p.h
index c886ba78d2ee..aac1b0b2ce3d 100644
--- a/hw/9pfs/9p.h
+++ b/hw/9pfs/9p.h
@@ -124,6 +124,11 @@ typedef struct {
uint8_t id;
uint16_t tag_le;
} QEMU_PACKED P9MsgHeader;
+/* According to the specification, 9p messages start with a 7-byte header.
+ * Since most of the code uses this header size in literal form, we must be
+ * sure this is indeed the case.
+ */
+QEMU_BUILD_BUG_ON(sizeof(P9MsgHeader) != 7);
struct V9fsPDU
{
diff --git a/hw/9pfs/virtio-9p-device.c b/hw/9pfs/virtio-9p-device.c
index 3380bfc0c551..1a68c1622d3a 100644
--- a/hw/9pfs/virtio-9p-device.c
+++ b/hw/9pfs/virtio-9p-device.c
@@ -53,17 +53,15 @@ static void handle_9p_output(VirtIODevice *vdev, VirtQueue *vq)
goto out_free_pdu;
}
- if (elem->in_num == 0) {
+ if (iov_size(elem->in_sg, elem->in_num) < 7) {
virtio_error(vdev,
"The guest sent a VirtFS request without space for "
"the reply");
goto out_free_req;
}
- QEMU_BUILD_BUG_ON(sizeof(out) != 7);
- len = iov_to_buf(elem->out_sg, elem->out_num, 0,
- &out, sizeof(out));
- if (len != sizeof(out)) {
+ len = iov_to_buf(elem->out_sg, elem->out_num, 0, &out, 7);
+ if (len != 7) {
virtio_error(vdev, "The guest sent a malformed VirtFS request: "
"header size is %zd, should be 7", len);
goto out_free_req;
next prev parent reply other threads:[~2017-06-23 6:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 6:44 [Qemu-devel] [PATCH v4 0/4] 9pfs: handle transport errors Greg Kurz
2017-06-23 6:45 ` [Qemu-devel] [PATCH v4 1/4] virtio-9p: record element after sanity checks Greg Kurz
2017-06-23 6:45 ` Greg Kurz [this message]
2017-06-23 6:45 ` [Qemu-devel] [PATCH v4 3/4] virtio-9p: break device if buffers are misconfigured Greg Kurz
2017-06-26 23:22 ` Stefano Stabellini
2017-06-27 6:54 ` Greg Kurz
2017-06-27 23:34 ` Stefano Stabellini
2017-06-28 11:22 ` Greg Kurz
2017-06-28 18:54 ` Stefano Stabellini
2017-06-28 19:54 ` Greg Kurz
2017-06-28 19:59 ` Stefano Stabellini
2017-06-23 6:45 ` [Qemu-devel] [PATCH v4 4/4] 9pfs: handle transport errors in pdu_complete() Greg Kurz
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=149820031604.7187.14987200901766883821.stgit@bahia.lan \
--to=groug@kaod.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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).