qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: yuchenlin@synology.com, qemu-devel@nongnu.org
Cc: famz@redhat.com, "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH] vmdk: return ENOTSUP before offset overflow
Date: Thu, 22 Mar 2018 07:55:42 -0500	[thread overview]
Message-ID: <cede55a3-a5e0-c98a-5d03-ff68a0305ecd@redhat.com> (raw)
In-Reply-To: <20180322024056.29599-1-yuchenlin@synology.com>

On 03/21/2018 09:40 PM, yuchenlin--- via Qemu-devel wrote:
> 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)

Please spell this '(2ULL * 1024 * 1024 * 1024 * 1024)', or even rebase 
it on top of Phillipe's BYTE-based definitions as '2 * T_BYTE' (v2 
proposed a cunits.h, although v3 is still pending posting and may rename 
the header units.h)

https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg01077.html

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

      parent reply	other threads:[~2018-03-22 12:55 UTC|newest]

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

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=cede55a3-a5e0-c98a-5d03-ff68a0305ecd@redhat.com \
    --to=eblake@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yuchenlin@synology.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).