qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block: Fix bdrv_commit return value
Date: Fri, 24 Jan 2014 10:56:45 -0500	[thread overview]
Message-ID: <20140124155645.GA19754@localhost.localdomain> (raw)
In-Reply-To: <1390568901-25060-1-git-send-email-kwolf@redhat.com>

On Fri, Jan 24, 2014 at 02:08:21PM +0100, Kevin Wolf wrote:
> bdrv_commit() could return 0 or 1 on success, depending on whether or
> now the last sector was allocated in the overlay and whether the overlay
> format had a .bdrv_make_empty callback.
> 
> Most callers ignored it, but qemu-img commit would print an error
> message while the operation actually succeeded.
> 
> Also clean up the handling of I/O errors to return the real error code
> instead of -EIO.
> 
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  block.c | 15 ++++++++++-----
>  1 file changed, 10 insertions(+), 5 deletions(-)
> 
> diff --git a/block.c b/block.c
> index 3e0994b..7d22ca9 100644
> --- a/block.c
> +++ b/block.c
> @@ -2061,13 +2061,13 @@ int bdrv_commit(BlockDriverState *bs)
>              goto ro_cleanup;
>          }
>          if (ret) {
> -            if (bdrv_read(bs, sector, buf, n) != 0) {
> -                ret = -EIO;
> +            ret = bdrv_read(bs, sector, buf, n);
> +            if (ret < 0) {
>                  goto ro_cleanup;
>              }
>  
> -            if (bdrv_write(bs->backing_hd, sector, buf, n) != 0) {
> -                ret = -EIO;
> +            ret = bdrv_write(bs->backing_hd, sector, buf, n);
> +            if (ret < 0) {
>                  goto ro_cleanup;
>              }
>          }
> @@ -2075,6 +2075,9 @@ int bdrv_commit(BlockDriverState *bs)
>  
>      if (drv->bdrv_make_empty) {
>          ret = drv->bdrv_make_empty(bs);
> +        if (ret < 0) {
> +            goto ro_cleanup;
> +        }

QED has a .bdrv_make_empty implementation, but it is a stub that
always returns -ENOTSUP.

Prior to this patch, a commit of a QED snapshot would complete OK, but
return an error saying "Image is already committed" (Which almost
seems like a non-error error).

Now, we'll skip ahead to cleanup.

I think we should either: 1) filter out -ENOTSUP here, or 2) remove
the stub from QED

>          bdrv_flush(bs);
>      }
>  
> @@ -2082,9 +2085,11 @@ int bdrv_commit(BlockDriverState *bs)
>       * Make sure all data we wrote to the backing device is actually
>       * stable on disk.
>       */
> -    if (bs->backing_hd)
> +    if (bs->backing_hd) {
>          bdrv_flush(bs->backing_hd);
> +    }
>  
> +    ret = 0;
>  ro_cleanup:
>      g_free(buf);
>  
> -- 
> 1.8.1.4
> 

  parent reply	other threads:[~2014-01-24 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 13:08 [Qemu-devel] [PATCH] block: Fix bdrv_commit return value Kevin Wolf
2014-01-24 15:39 ` Benoît Canet
2014-01-24 15:56 ` Jeff Cody [this message]
2014-01-24 16:00   ` Kevin Wolf
2014-01-24 16:21     ` Jeff Cody

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=20140124155645.GA19754@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=kwolf@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).