From: Alberto Garcia <berto@igalia.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Qemu-devel@nongnu.org" <Qemu-devel@nongnu.org>,
qemu block <qemu-block@nongnu.org>, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] help debugging throttle crash
Date: Mon, 3 Apr 2017 17:24:43 +0200 [thread overview]
Message-ID: <20170403152443.GA20459@igalia.com> (raw)
In-Reply-To: <13fddf65-e573-cf01-593d-6b02a3071721@redhat.com>
On Mon, Apr 03, 2017 at 09:07:02AM -0500, Eric Blake wrote:
> At this point, it looks like no one is calling
> throttle_group_unregister_blk() as a result of the 'device_del',
> which leaves stale memory around
I see, I can also reproduce this very easily.
I wonder if it's not enough to simply disable I/O limits when a
BlockBackend is deleted?
--- a/block/block-backend.c
+++ b/block/block-backend.c
@@ -230,6 +230,9 @@ static void blk_delete(BlockBackend *blk)
assert(!blk->refcnt);
assert(!blk->name);
assert(!blk->dev);
+ if (blk->public.throttle_state) {
+ blk_io_limits_disable(blk);
+ }
if (blk->root) {
blk_remove_bs(blk);
}
Berto
next prev parent reply other threads:[~2017-04-03 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 14:07 [Qemu-devel] help debugging throttle crash Eric Blake
2017-04-03 15:24 ` Alberto Garcia [this message]
2017-04-06 18:57 ` Eric Blake
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=20170403152443.GA20459@igalia.com \
--to=berto@igalia.com \
--cc=Qemu-devel@nongnu.org \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@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 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).