From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
"Stefan Hajnoczi" <shajnocz@redhat.com>,
"Fam Zheng" <famz@redhat.com>,
peterx@redhat.com, "Andreas Färber" <afaerber@suse.de>,
"Manos Pitsidianakis" <el13635@mail.ntua.gr>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v4 5/5] aio: fix assert when remove poll during destroy
Date: Thu, 28 Sep 2017 10:59:58 +0800 [thread overview]
Message-ID: <20170928025958.1420-6-peterx@redhat.com> (raw)
In-Reply-To: <20170928025958.1420-1-peterx@redhat.com>
From: Stefan Hajnoczi <stefanha@redhat.com>
After iothread is enabled internally inside QEMU with GMainContext, we
may encounter this warning when destroying the iothread:
(qemu-system-x86_64:19925): GLib-CRITICAL **: g_source_remove_poll:
assertion '!SOURCE_DESTROYED (source)' failed
The problem is that g_source_remove_poll() does not allow to remove one
source from array if the source is detached from its owner
context. (peterx: which IMHO does not make much sense)
Fix it on QEMU side by avoid calling g_source_remove_poll() if we know
the object is during destruction, and we won't leak anything after all
since the array will be gone soon cleanly even with that fd.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
[peterx: write the commit message]
Signed-off-by: Peter Xu <peterx@redhat.com>
---
util/aio-posix.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/util/aio-posix.c b/util/aio-posix.c
index 2d51239ec6..5946ac09f0 100644
--- a/util/aio-posix.c
+++ b/util/aio-posix.c
@@ -223,7 +223,14 @@ void aio_set_fd_handler(AioContext *ctx,
return;
}
- g_source_remove_poll(&ctx->source, &node->pfd);
+ /* If the GSource is in the process of being destroyed then
+ * g_source_remove_poll() causes an assertion failure. Skip
+ * removal in that case, because glib cleans up its state during
+ * destruction anyway.
+ */
+ if (!g_source_is_destroyed(&ctx->source)) {
+ g_source_remove_poll(&ctx->source, &node->pfd);
+ }
/* If the lock is held, just mark the node as deleted */
if (qemu_lockcnt_count(&ctx->list_lock)) {
--
2.13.5
next prev parent reply other threads:[~2017-09-28 3:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 2:59 [Qemu-devel] [PATCH v4 0/5] iothread: allow to create internal iothreads Peter Xu
2017-09-28 2:59 ` [Qemu-devel] [PATCH v4 1/5] qom: provide root container for internal objs Peter Xu
2017-09-28 7:11 ` Fam Zheng
2017-09-28 2:59 ` [Qemu-devel] [PATCH v4 2/5] iothread: provide helpers for internal use Peter Xu
2017-09-28 2:59 ` [Qemu-devel] [PATCH v4 3/5] iothread: export iothread_stop() Peter Xu
2017-09-28 2:59 ` [Qemu-devel] [PATCH v4 4/5] iothread: delay the context release to finalize Peter Xu
2017-09-28 2:59 ` Peter Xu [this message]
2017-09-28 7:11 ` [Qemu-devel] [PATCH v4 5/5] aio: fix assert when remove poll during destroy Fam Zheng
2017-09-28 9:59 ` Stefan Hajnoczi
2017-09-28 10:28 ` [Qemu-devel] [PATCH v4 0/5] iothread: allow to create internal iothreads Stefan Hajnoczi
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=20170928025958.1420-6-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=afaerber@suse.de \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=el13635@mail.ntua.gr \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shajnocz@redhat.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).