From: Kevin Wolf <kwolf@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/2] qcow2_create() error handling fixes
Date: Fri, 08 Oct 2010 12:11:02 +0200 [thread overview]
Message-ID: <4CAEEE36.3030903@redhat.com> (raw)
In-Reply-To: <1286483105-9768-1-git-send-email-ehabkost@redhat.com>
Am 07.10.2010 22:25, schrieb Eduardo Habkost:
> From: Eduardo Habkost <ehabkost@raisama.net>
>
> Hi,
>
> Here are two small fixes on qcow2_create() error handling.
>
> Eduardo Habkost (2):
> fix fd leak on a qcow2_create2() error path
> check for close() errors on qcow2_create()
A while ago I sent a patch to completely rewrite qcow_create using qemu
block layer functions. I didn't submit it for inclusion yet because it
makes some assumptions in qemu-iotests invalid and the test cases need
to be fixed first.
In the new version, your first patch wouldn't be needed. However, for
the second one, I think we have a problem today:
void bdrv_close(BlockDriverState *bs);
We need to convert bdrv_close to be able to return error values and to
pass them on up to the first caller (which is qemu-img in this case).
I'll have a look at fixing the test cases and bdrv_close. If I can't get
it fixed easily, I'll consider your patches.
Kevin
prev parent reply other threads:[~2010-10-08 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 20:25 [Qemu-devel] [PATCH 0/2] qcow2_create() error handling fixes Eduardo Habkost
2010-10-07 20:25 ` [Qemu-devel] [PATCH 1/2] fix fd leak on one qcow2_create2() error path Eduardo Habkost
2010-10-08 9:36 ` Stefan Hajnoczi
2010-10-07 20:25 ` [Qemu-devel] [PATCH 2/2] check for close() errors on qcow2_create() Eduardo Habkost
2010-10-08 9:28 ` Stefan Hajnoczi
2010-10-08 15:29 ` Eduardo Habkost
2010-10-08 10:14 ` [Qemu-devel] " Kevin Wolf
2010-10-08 17:39 ` Eduardo Habkost
2010-10-08 10:11 ` 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=4CAEEE36.3030903@redhat.com \
--to=kwolf@redhat.com \
--cc=ehabkost@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.