qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Evgeny Budilovsky <evgeny.budilovsky@ravellosystems.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] allow reading variable size vmdk descriptor files
Date: Wed, 12 Jun 2013 12:30:27 +0200	[thread overview]
Message-ID: <20130612103027.GB2677@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1371024284-3572-1-git-send-email-evgeny.budilovsky@ravellosystems.com>

Am 12.06.2013 um 10:04 hat Evgeny Budilovsky geschrieben:
> The hard-coded 2k buffer on the stack won't allow reading big descriptor
> files which can be generated when storing big images (For example 500G
> vmdk splitted to 2G chunks).
> 
> Signed-off-by: Evgeny Budilovsky <evgeny.budilovsky@ravellosystems.com>
> ---
>  block/vmdk.c |   28 +++++++++++++++++++++-------
>  1 file changed, 21 insertions(+), 7 deletions(-)
> 
> diff --git a/block/vmdk.c b/block/vmdk.c
> index 608daaf..1bc944b 100644
> --- a/block/vmdk.c
> +++ b/block/vmdk.c
> @@ -719,27 +719,41 @@ static int vmdk_open_desc_file(BlockDriverState *bs, int flags,
>                                 int64_t desc_offset)
>  {
>      int ret;
> -    char buf[2048];
> +    char *buf = NULL;
>      char ct[128];
>      BDRVVmdkState *s = bs->opaque;
> +    int64_t size;
> 
> -    ret = bdrv_pread(bs->file, desc_offset, buf, sizeof(buf));
> +    size = bdrv_get_allocated_file_size(bs);
> +    if (size < 0) {
> +        return -EINVAL;
> +    }
> +
> +    buf = g_malloc0(size+1);

This is an unbounded allocation. Not sure if this is a good idea. Can we
restrict the maximum size to something reasonably small, like a megabyte?

Kevin

  parent reply	other threads:[~2013-06-12 10:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12  8:04 [Qemu-devel] [PATCH] allow reading variable size vmdk descriptor files Evgeny Budilovsky
2013-06-12 10:17 ` Stefan Hajnoczi
2013-06-12 10:38   ` Evgeny Budilovsky
2013-06-12 10:30 ` Kevin Wolf [this message]
2013-06-12 10:41   ` Evgeny Budilovsky
2013-06-12 11:06 ` [Qemu-devel] [PATCH v2] " Evgeny Budilovsky
2013-06-12 14:15   ` Stefan Hajnoczi
2013-06-12 15:17   ` Kevin Wolf
  -- strict thread matches above, loose matches on Subject: below --
2013-06-12  7:32 [Qemu-devel] [PATCH] " Evgeny Budilovsky
2013-06-12  7:08 Evgeny Budilovsky
2013-06-13 21:15 ` Don Slutz
2013-06-14  6:41   ` Evgeny Budilovsky
2013-06-25 10:16     ` Don Slutz

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=20130612103027.GB2677@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=evgeny.budilovsky@ravellosystems.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).