From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56012) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cwGzc-0002rj-MI for qemu-devel@nongnu.org; Thu, 06 Apr 2017 19:39:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cwGzb-0003mS-PK for qemu-devel@nongnu.org; Thu, 06 Apr 2017 19:39:08 -0400 Date: Fri, 7 Apr 2017 07:38:56 +0800 From: Fam Zheng Message-ID: <20170406233856.GC4618@lemon> References: <20170406142527.25835-1-famz@redhat.com> <20170406142527.25835-2-famz@redhat.com> <20170406143607.GH4341@noname.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170406143607.GH4341@noname.redhat.com> Subject: Re: [Qemu-devel] [PATCH for-2.9 1/5] block: Fix unpaired aio_disable_external in external snapshot List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: qemu-devel@nongnu.org, Paolo Bonzini , qemu-block@nongnu.org, Ed Swierk , Max Reitz , Stefan Hajnoczi On Thu, 04/06 16:36, Kevin Wolf wrote: > Am 06.04.2017 um 16:25 hat Fam Zheng geschrieben: > > bdrv_replace_child_noperm tries to hand over the quiesce_counter state > > from old bs to the new one, but if they are not on the same aio context > > this causes unbalance. > > > > Fix this by forcing callers to move the aio context first, and assert > > it. > > > > Reported-by: Ed Swierk > > Signed-off-by: Fam Zheng > > --- > > block.c | 3 +++ > > blockdev.c | 4 ++-- > > 2 files changed, 5 insertions(+), 2 deletions(-) > > > > diff --git a/block.c b/block.c > > index 927ba89..8893ac1 100644 > > --- a/block.c > > +++ b/block.c > > @@ -1752,6 +1752,9 @@ static void bdrv_replace_child_noperm(BdrvChild *child, > > { > > BlockDriverState *old_bs = child->bs; > > > > + if (old_bs && new_bs) { > > + assert(bdrv_get_aio_context(old_bs) == bdrv_get_aio_context(new_bs)); > > + } > > if (old_bs) { > > if (old_bs->quiesce_counter && child->role->drained_end) { > > child->role->drained_end(child); > > Can we move this to a separate patch and also add this hunk for > asserting the same thing for newly attached child nodes: > > @@ -1852,6 +1855,7 @@ BdrvChild *bdrv_attach_child(BlockDriverState *parent_bs, > bdrv_get_cumulative_perm(parent_bs, &perm, &shared_perm); > > assert(parent_bs->drv); > + assert(bdrv_get_aio_context(parent_bs) == bdrv_get_aio_context(child_bs)); > parent_bs->drv->bdrv_child_perm(parent_bs, NULL, child_role, > perm, shared_perm, &perm, &shared_perm); OK, will do.