qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, qemu-stable@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] cpus: Let vm_stop[_force_state]() always flush block devices
Date: Thu, 18 Jul 2013 14:55:48 +0200	[thread overview]
Message-ID: <20130718125548.GL3582@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1374151939-3883-1-git-send-email-kwolf@redhat.com>

Am 18.07.2013 um 14:52 hat Kevin Wolf geschrieben:
> Even if the VM is already stopped, we cannot assume that all data has
> already been successfully flushed to disk. The flush during the previous
> vm_stop() could have failed.
> 
> Run bdrv_flush_all() unconditionally so that we get an error each time
> if the block device isn't really flushed.
> 

Oops, forgot it again:

Cc: qemu-stable@nongnu.org

> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  cpus.c | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/cpus.c b/cpus.c
> index 8062cdd..2509eb5 100644
> --- a/cpus.c
> +++ b/cpus.c
> @@ -443,11 +443,12 @@ static int do_vm_stop(RunState state)
>          pause_all_vcpus();
>          runstate_set(state);
>          vm_state_notify(0, state);
> -        bdrv_drain_all();
> -        ret = bdrv_flush_all();
>          monitor_protocol_event(QEVENT_STOP, NULL);
>      }
>  
> +    bdrv_drain_all();
> +    ret = bdrv_flush_all();
> +
>      return ret;
>  }
>  
> @@ -1126,7 +1127,9 @@ int vm_stop_force_state(RunState state)
>          return vm_stop(state);
>      } else {
>          runstate_set(state);
> -        return 0;
> +        /* Make sure to return an error if the flush in a previous vm_stop()
> +         * failed. */
> +        return bdrv_flush_all();
>      }
>  }
>  
> -- 
> 1.8.1.4
> 

  reply	other threads:[~2013-07-18 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 12:52 [Qemu-devel] [PATCH] cpus: Let vm_stop[_force_state]() always flush block devices Kevin Wolf
2013-07-18 12:55 ` Kevin Wolf [this message]
2013-07-18 13:02   ` Eric Blake
2013-07-19  4:24 ` Stefan Hajnoczi

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=20130718125548.GL3582@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).