All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Stefan Weil <sw@weilnetz.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] block: Fix error report for wrong file format
Date: Thu, 17 Jan 2013 13:10:28 +0100	[thread overview]
Message-ID: <50F7EA34.9020008@redhat.com> (raw)
In-Reply-To: <20130117083320.GA19607@stefanha-thinkpad.redhat.com>

Am 17.01.2013 09:33, schrieb Stefan Hajnoczi:
> On Wed, Jan 16, 2013 at 07:53:35PM +0100, Stefan Weil wrote:
>> Am 15.12.2012 15:09, schrieb Stefan Weil:
>>> These patches improve the error report if the file format was
>>> specified explicitly (example: -drive file=myfile,format=qcow2)
>>> and the given format does not match the real format.
>>>
>>> This fixes those bugs:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=556482
>>> https://bugs.launchpad.net/qemu/+bug/1090600
>>>
>>> [PATCH 1/4] block: Add special error code for wrong format
>>> [PATCH 2/4] block: Improve error report for wrong format
>>> [PATCH 3/4] block: Use new error code for wrong format in selected
>>> [PATCH 4/4] block/vdi: Improved return values from vdi_open and
>>
>> Hi Stefan und Kevin,
>>
>> these patches are still in my local queue.
>>
>> Do you plan to add them to the block queue, or would
>> you prefer another solution for the open bug reports?
> 
> Looks okay to me.  I'm not thrilled about introducing a non-system error
> code, would have rather have used EINVAL or ENOTTY.  But that's not a
> killer and I see the reason you chose to do that.
> 
> Kevin: Any comments before I merge this?

Yes, I commented on the patches. I think the minimum that should change
is moving the error code definition to where other error codes are
defined in order to avoid future collisions.

Ideally we'd convert bdrv_open to Error and avoid all this error code
stuff, but I'm not requesting this now.

Kevin

      reply	other threads:[~2013-01-17 12:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-15 14:09 [Qemu-devel] [PATCH 0/4] block: Fix error report for wrong file format Stefan Weil
2012-12-15 14:09 ` [Qemu-devel] [PATCH 1/4] block: Add special error code for wrong format Stefan Weil
2012-12-18 14:34   ` Stefan Hajnoczi
2013-01-17 12:01   ` Kevin Wolf
2012-12-15 14:09 ` [Qemu-devel] [PATCH 2/4] block: Improve error report " Stefan Weil
2012-12-17 15:08   ` Luiz Capitulino
2012-12-15 14:09 ` [Qemu-devel] [PATCH 3/4] block: Use new error code for wrong format in selected block drivers Stefan Weil
2012-12-15 15:54   ` Don Slutz
2012-12-15 14:09 ` [Qemu-devel] [PATCH 4/4] block/vdi: Improved return values from vdi_open and other small fixes Stefan Weil
2013-01-17 12:08   ` Kevin Wolf
2013-01-16 18:53 ` [Qemu-devel] [PATCH 0/4] block: Fix error report for wrong file format Stefan Weil
2013-01-17  8:33   ` Stefan Hajnoczi
2013-01-17 12:10     ` 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=50F7EA34.9020008@redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.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 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.