qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: John Snow <jsnow@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
	wangxiaolong@ucloud.cn
Subject: Re: [Qemu-devel] Fwd: qemu drive mirror assert fault
Date: Tue, 05 May 2015 12:13:24 +0200	[thread overview]
Message-ID: <554897C4.20804@redhat.com> (raw)
In-Reply-To: <20150505073609.GA9322@ad.nay.redhat.com>



On 05/05/2015 09:36, Fam Zheng wrote:
> Since the gdb output is suggesting 1.5.3, it's worth to trying 2.3 which has
> this:
> 
>     commit c4237dfa635900e4d1cdc6038d5efe3507f45f0c
>     Author: Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>
>     Date:   Thu Nov 27 12:40:46 2014 +0300
> 
>         block: fix spoiling all dirty bitmaps by mirror and migration
> 
>         Mirror and migration use dirty bitmaps for their purposes, and since
>         commit [block: per caller dirty bitmap] they use their own bitmaps, not
>         the global one. But they use old functions bdrv_set_dirty and
>         bdrv_reset_dirty, which change all dirty bitmaps.
> 
>         Named dirty bitmaps series by Fam and Snow are affected: mirroring and
>         migration will spoil all (not related to this mirroring or migration)
>         named dirty bitmaps.
> 
>         This patch fixes this by adding bdrv_set_dirty_bitmap and
>         bdrv_reset_dirty_bitmap, which change concrete bitmap. Also, to prevent
>         such mistakes in future, old functions bdrv_(set,reset)_dirty are made
>         static, for internal block usage.
> 
>         Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>
>         CC: John Snow <jsnow@redhat.com>
>         CC: Fam Zheng <famz@redhat.com>
>         CC: Denis V. Lunev <den@openvz.org>
>         CC: Stefan Hajnoczi <stefanha@redhat.com>
>         CC: Kevin Wolf <kwolf@redhat.com>
>         Reviewed-by: John Snow <jsnow@redhat.com>
>         Reviewed-by: Fam Zheng <famz@redhat.com>
>         Message-id: 1417081246-3593-1-git-send-email-vsementsov@parallels.com
>         Signed-off-by: Max Reitz <mreitz@redhat.com>

I don't think this commit is relevant.  The bug is caused by
bdrv_co_discard clearing the bitmap (which is not supported during
iteration, and is caught by the assertion).  That bdrv_reset_dirty is
not removed by the commit you pointed out.

Paolo

  reply	other threads:[~2015-05-05 10:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_D4C0F8C0FE9E16802F5FF410@qq.com>
2015-04-30 15:50 ` [Qemu-devel] Fwd: qemu drive mirror assert fault Paolo Bonzini
2015-04-30 15:54   ` Paolo Bonzini
2015-05-05  7:36   ` Fam Zheng
2015-05-05 10:13     ` Paolo Bonzini [this message]
2015-05-05 10:27       ` Fam Zheng
2015-05-05 11:48         ` Kevin Wolf
2015-05-05 11:49           ` Paolo Bonzini
2015-05-05 11:54             ` Paolo Bonzini
2015-05-05 13:03             ` Kevin Wolf
2015-05-05 13:07               ` Paolo Bonzini
2015-05-05 13:31                 ` Kevin Wolf
2015-05-05 12:09           ` Fam Zheng

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=554897C4.20804@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wangxiaolong@ucloud.cn \
    /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).