From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] block: Inactivate all children
Date: Wed, 4 May 2016 12:12:42 +0200 [thread overview]
Message-ID: <20160504101242.GC14972@noname.str.redhat.com> (raw)
In-Reply-To: <1461030177-29144-3-git-send-email-famz@redhat.com>
Am 19.04.2016 um 03:42 hat Fam Zheng geschrieben:
> Currently we only inactivate the top BDS. Actually bdrv_inactivate
> should be the opposite of bdrv_invalidate_cache.
>
> Recurse into the whole subtree instead.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
Did you actually test this?
I would expect that bs->drv->bdrv_inactivate() fails now (as in
assertion failure) if it has anything to flush to the image because
bs->file has already be inactivated before. I think children need to be
inactived after their parents.
Nodes with multiple parents could actually become even more
interesting...
Kevin
> block.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/block.c b/block.c
> index fa8b38f..9a84ed1 100644
> --- a/block.c
> +++ b/block.c
> @@ -3260,8 +3260,16 @@ void bdrv_invalidate_cache_all(Error **errp)
>
> static int bdrv_inactivate(BlockDriverState *bs)
> {
> + BdrvChild *child;
> int ret;
>
> + QLIST_FOREACH(child, &bs->children, next) {
> + ret = bdrv_inactivate(child->bs);
> + if (ret < 0) {
> + return ret;
> + }
> + }
> +
> if (bs->drv->bdrv_inactivate) {
> ret = bs->drv->bdrv_inactivate(bs);
> if (ret < 0) {
> --
> 2.8.0
>
next prev parent reply other threads:[~2016-05-04 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 1:42 [Qemu-devel] [PATCH 0/2] block: More complete inactivate/invalidate of on graph Fam Zheng
2016-04-19 1:42 ` [Qemu-devel] [PATCH 1/2] block: Invalidate all children Fam Zheng
2016-04-19 8:44 ` Changlong Xie
2016-04-19 12:23 ` Fam Zheng
2016-05-04 10:10 ` Kevin Wolf
2016-05-05 0:32 ` Fam Zheng
2016-04-19 1:42 ` [Qemu-devel] [PATCH 2/2] block: Inactivate " Fam Zheng
2016-05-04 10:12 ` Kevin Wolf [this message]
2016-05-05 0:32 ` Fam Zheng
2016-05-06 7:49 ` Kevin Wolf
2016-05-10 3:23 ` Fam Zheng
2016-05-10 8:33 ` Kevin Wolf
2016-05-11 1:51 ` 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=20160504101242.GC14972@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=famz@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.