qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chai Wen <chaiw.fnst@cn.fujitsu.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
	stefanha@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH resend] block: fix wrong order in live block migration setup
Date: Wed, 4 Jun 2014 19:36:30 +0800	[thread overview]
Message-ID: <538F04BE.5020309@cn.fujitsu.com> (raw)
In-Reply-To: <20140604092309.GC26902@stefanha-thinkpad.redhat.com>

On 06/04/2014 05:23 PM, Stefan Hajnoczi wrote:

> On Wed, Jun 04, 2014 at 11:47:37AM +0800, chai wen wrote:
>>
>> The function init_blk_migration is better to be called before
>> set_dirty_tracking as the reasons below.
>>
>> If we want to track dirty blocks via dirty_maps on a BlockDriverState
>> when doing live block-migration, its correspoding 'BlkMigDevState' should be
>> added to block_mig_state.bmds_list first for subsequent processing.
>> Otherwise set_dirty_tracking will do nothing on an empty list than allocating
>> dirty_bitmaps for them. And bdrv_get_dirty_count will access the 
>> bmds->dirty_maps directly, then there would be a segfault triggered.
>>
>> If the set_dirty_tracking fails, qemu_savevm_state_cancel will handle
>> the cleanup of init_blk_migration automatically.
>>
>>
>> Reviewed-by: Fam Zheng <famz@redhat.com>
>> Signed-off-by: chai wen <chaiw.fnst@cn.fujitsu.com>
>> ---
>>  block-migration.c |    3 +--
>>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> Thanks, applied to my block tree:
> https://github.com/stefanha/qemu/commits/block
> 


OK, thanks for your attention about this fix. :)

thanks
chai wen

> Stefan
> .
> 



-- 
Regards

Chai Wen

      reply	other threads:[~2014-06-04 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  3:47 [Qemu-devel] [PATCH resend] block: fix wrong order in live block migration setup chai wen
2014-06-04  9:23 ` Stefan Hajnoczi
2014-06-04 11:36   ` Chai Wen [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=538F04BE.5020309@cn.fujitsu.com \
    --to=chaiw.fnst@cn.fujitsu.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@gmail.com \
    --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).