qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] block/vdi: Allow disk images of size 0
Date: Fri, 07 May 2010 10:02:48 +0200	[thread overview]
Message-ID: <4BE3C928.3070005@redhat.com> (raw)
In-Reply-To: <1273172027-20819-1-git-send-email-weil@mail.berlios.de>

Am 06.05.2010 20:53, schrieb Stefan Weil:
> Even it is not very useful, users may create images of size 0.
> 
> Without the special option CONFIG_ZERO_MALLOC, qemu_mallocz
> aborts execution when it is told to allocate 0 bytes,
> so avoid this kind of call.
> 
> Cc: Kevin Wolf <kwolf@redhat.com>
> Signed-off-by: Stefan Weil <weil@mail.berlios.de>

This stupid qemu_malloc behaviour only ever introduces bugs instead of
avoiding them... *sigh*

Thanks, applied to the block branch.

Kevin

      reply	other threads:[~2010-05-07  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 18:53 [Qemu-devel] [PATCH] block/vdi: Allow disk images of size 0 Stefan Weil
2010-05-07  8:02 ` Kevin Wolf [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=4BE3C928.3070005@redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /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).