From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] qemu-img.c: Clean up handling of image size in img_create()
Date: Wed, 08 Dec 2010 07:30:58 +0100 [thread overview]
Message-ID: <4CFF2622.7000107@redhat.com> (raw)
In-Reply-To: <AANLkTikLhAtCw2bYqtwYXFOCsHseWc3DZWXbyW55TxAd@mail.gmail.com>
On 12/07/10 21:36, Stefan Hajnoczi wrote:
> On Tue, Dec 7, 2010 at 5:39 PM, <Jes.Sorensen@redhat.com> wrote:
>> // The size for the image must always be specified, with one exception:
>> // If we are using a backing file, we can obtain the size from there
>> - if (get_option_parameter(param, BLOCK_OPT_SIZE)->value.n == -1) {
>> -
>> + if (get_option_parameter(param, BLOCK_OPT_SIZE)->value.n == 0) {
>> QEMUOptionParameter *backing_file =
>> get_option_parameter(param, BLOCK_OPT_BACKING_FILE);
>> QEMUOptionParameter *backing_fmt =
>
> Today it is possible to create 0 byte sized images. Your patch will
> change that:
> If there is a backing file, then the size will be taken from the backing file.
> If there is no backing file, then an error about missing size will be
> printed, even though a size of 0 has been given.
>
> I don't think 0 sized images are very useful, but I'm not sure we
> should make this change.
The old code also fails if there is no size, except for when a backing
file is present.
I hadn't thought of the zero sized file, but on the other hand, I don't
see it being useful.
I would like to make this change to get the option handling cleaned up
as it allows me to refactor the code in img_create().
Cheers,
Jes
next prev parent reply other threads:[~2010-12-08 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 17:39 [Qemu-devel] [PATCH 1/1] qemu-img.c: Clean up handling of image size in img_create() Jes.Sorensen
2010-12-07 20:36 ` Stefan Hajnoczi
2010-12-08 6:30 ` Jes Sorensen [this message]
2010-12-08 8:54 ` Kevin Wolf
2010-12-08 9:14 ` Jes Sorensen
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=4CFF2622.7000107@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).