qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Shahar Havivi <shaharh@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Block migration fail,	ignore error from bdrv_getlength
Date: Mon, 12 Jul 2010 10:09:21 +0200	[thread overview]
Message-ID: <4C3ACDB1.1090108@redhat.com> (raw)
In-Reply-To: <20100710155902.GA7402@redhat.com>

Am 10.07.2010 17:59, schrieb Shahar Havivi:
> When there is no block driver associate with BlockDriverState bdrv_getlength
> returns -ENOMEDIUM that cause block migration to fail
> 
> v2:
> fix sectors<0 to sectors<=0

Please put the changes between patch versions below the --- line so that
git am ignores it.

> 
> Signed-off-by: Shahar Havivi <shaharh@redhat.com>
> ---
>  block-migration.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/block-migration.c b/block-migration.c
> index 7db6f02..a77106e 100644
> --- a/block-migration.c
> +++ b/block-migration.c
> @@ -238,7 +238,7 @@ static void init_blk_migration_it(void *opaque, BlockDriverState *bs)
>  
>      if (!bdrv_is_read_only(bs)) {
>          sectors = bdrv_getlength(bs) >> BDRV_SECTOR_BITS;
> -        if (sectors == 0) {
> +        if (sectors <= 0) {
>              return;
>          }
>  

Dealing with -errno shifted by 9 looks really strange, but it should be
correct (sectors being -1 for error cases in practice).

Thanks, applied to the block branch.

Kevin

      reply	other threads:[~2010-07-12  8:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10 15:59 [Qemu-devel] [PATCH v2] Block migration fail, ignore error from bdrv_getlength Shahar Havivi
2010-07-12  8:09 ` 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=4C3ACDB1.1090108@redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shaharh@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).