From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [RFC v3 0/6] block: Error parameter for opening/creating images
Date: Tue, 10 Sep 2013 16:37:44 +0200 [thread overview]
Message-ID: <20130910143744.GF2797@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1378482755-31669-1-git-send-email-mreitz@redhat.com>
Am 06.09.2013 um 17:52 hat Max Reitz geschrieben:
> This RFC adds an Error ** parameter to bdrv_open, bdrv_file_open,
> bdrv_create and the respective functions provided by a block driver.
>
> This results in more specific error information than just -errno provided
> to the user when opening or creating images (disregarding the fact that
> block drivers often already use error_report, which is generally changed
> to error_setg through this patch).
>
> The sixth patch in this series changes the qcow2 block driver to set an
> example of usage in a block driver.
>
> Note that several I/O tests break by applying this RFC since they expect
> different error messages (generally, previously, an error message on
> image opening/creation consisted of two lines; the first of which would be
> generated by the driver through error_report, the second by the block
> layer itself through strerror(-ret); this patch is designed to merge these
> two lines into a single one). This applies to the tests 49, 51, 54 and 60.
Looks good to me now (except that it needs a rebase because it conflicts
with other recent patches in the block tree).
I guess it's time to address the qemu-iotests part and send out a
non-RFC series.
Kevin
prev parent reply other threads:[~2013-09-10 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 15:52 [Qemu-devel] [RFC v3 0/6] block: Error parameter for opening/creating images Max Reitz
2013-09-06 15:52 ` [Qemu-devel] [RFC v3 1/6] bdrv: Use "Error" for opening images Max Reitz
2013-09-06 15:52 ` [Qemu-devel] [RFC v3 2/6] bdrv: Use "Error" for creating images Max Reitz
2013-09-06 15:52 ` [Qemu-devel] [RFC v3 3/6] block: Error parameter for open functions Max Reitz
2013-09-06 15:52 ` [Qemu-devel] [RFC v3 4/6] block: Error parameter for create functions Max Reitz
2013-09-06 15:52 ` [Qemu-devel] [RFC v3 5/6] qemu-img create: Emit filename on error Max Reitz
2013-09-06 15:52 ` [Qemu-devel] [RFC v3 6/6] qcow2: Use Error parameter Max Reitz
2013-09-10 14:37 ` 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=20130910143744.GF2797@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.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).