qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: yuchenlin@synology.com
To: qemu-devel@nongnu.org
Cc: famz@redhat.com, yuchenlin <yuchenlin@synology.com>
Subject: [Qemu-devel] [PATCH] vmdk: return ENOTSUP before offset overflow
Date: Thu, 22 Mar 2018 10:40:56 +0800	[thread overview]
Message-ID: <20180322024056.29599-1-yuchenlin@synology.com> (raw)

From: yuchenlin <yuchenlin@synology.com>

VMDK has a hard limitation of extent size, which is due to the size of grain
table entry is 32 bits. It means it can only point to a grain located at
offset = 2^32. To prevent offset overflow and record a useless offset
in grain table. We should return un-support here.

Signed-off-by: yuchenlin <yuchenlin@synology.com>
---
 block/vmdk.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/block/vmdk.c b/block/vmdk.c
index f94c49a9c0..d8fc961940 100644
--- a/block/vmdk.c
+++ b/block/vmdk.c
@@ -47,6 +47,9 @@
 #define VMDK4_FLAG_MARKER (1 << 17)
 #define VMDK4_GD_AT_END 0xffffffffffffffffULL
 
+/* 2TB */
+#define VMDK_EXTENT_SIZE_LIMIT (2199023255552)
+
 #define VMDK_GTE_ZEROED 0x1
 
 /* VMDK internal error codes */
@@ -1645,6 +1648,9 @@ static int vmdk_pwritev(BlockDriverState *bs, uint64_t offset,
                 return ret;
             }
             if (m_data.valid) {
+                if (cluster_offset > VMDK_EXTENT_SIZE_LIMIT) {
+                    return -ENOTSUP;
+                }
                 /* update L2 tables */
                 if (vmdk_L2update(extent, &m_data,
                                   cluster_offset >> BDRV_SECTOR_BITS)
-- 
2.16.2

             reply	other threads:[~2018-03-22  2:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22  2:40 yuchenlin [this message]
2018-03-22  4:00 ` [Qemu-devel] [PATCH] vmdk: return ENOTSUP before offset overflow Fam Zheng
2018-03-22 12:55 ` Eric Blake

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=20180322024056.29599-1-yuchenlin@synology.com \
    --to=yuchenlin@synology.com \
    --cc=famz@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).