From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/3] another round of qemu-char fixes
Date: Thu, 18 Apr 2013 14:38:27 +0200 [thread overview]
Message-ID: <516FE943.1010106@redhat.com> (raw)
In-Reply-To: <516F8F50.3040301@redhat.com>
Il 18/04/2013 08:14, Gerd Hoffmann ha scritto:
> Thread 1 (Thread 0x7f9038188980 (LWP 27849)):
> ---Type <return> to continue, or q <return> to quit---
> #0 __lll_lock_wait () at
> ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136
> #1 0x00007f90366a9388 in _L_lock_854 () from /lib64/libpthread.so.0
> #2 0x00007f90366a9257 in __pthread_mutex_lock (mutex=0x7f903abb1538) at
> pthread_mutex_lock.c:61
> #3 0x00007f9037903c37 in ?? () from /lib64/libglib-2.0.so.0
> #4 0x00007f90383c5d96 in io_watch_poll_finalize (source=<value
> optimized out>)
> at /home/kraxel/projects/qemu/qemu-char.c:648
Hmm, this seems to be recursive locking. It sounded unlikely, but then
googling for "glib gsource finalize unlock" led to this:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946
and this:
https://mail.gnome.org/archives/commits-list/2010-November/msg01816.html
and this:
https://bugzilla.gnome.org/show_bug.cgi?id=586432
https://bugzilla.gnome.org/show_bug.cgi?id=626702
Comment 6 of the latter bug says that finalize-inside-finalize is in
fact broken without this fix. If this is RHEL6, you or Amit should file
a bug.
Paolo
next prev parent reply other threads:[~2013-04-18 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 11:10 [Qemu-devel] [PATCH 0/3] another round of qemu-char fixes Paolo Bonzini
2013-04-16 11:10 ` [Qemu-devel] [PATCH 1/3] qemu-char: use consistent idiom for removing sources Paolo Bonzini
2013-04-16 11:10 ` [Qemu-devel] [PATCH 2/3] qemu-char: simplify pty polling Paolo Bonzini
2013-04-16 11:10 ` [Qemu-devel] [PATCH 3/3] qemu-char: correct return value from chr_read functions Paolo Bonzini
2013-04-16 11:22 ` [Qemu-devel] [PATCH 0/3] another round of qemu-char fixes Gerd Hoffmann
2013-04-17 7:06 ` Gerd Hoffmann
2013-04-17 9:28 ` Paolo Bonzini
2013-04-17 10:17 ` Paolo Bonzini
2013-04-18 6:14 ` Gerd Hoffmann
2013-04-18 12:38 ` Paolo Bonzini [this message]
2013-04-18 12:54 ` Gerd Hoffmann
2013-04-18 13:11 ` Paolo Bonzini
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=516FE943.1010106@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=kraxel@redhat.com \
--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 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).