On Wed, Apr 04, 2018 at 03:53:05PM +0100, Stefan Hajnoczi wrote:
> On Wed, Apr 04, 2018 at 02:53:46PM +0800, Peter Xu wrote:
> > Free the AIO context earlier than the GMainContext (if we have) to
> > workaround a possible Glib bug. No functional change at all.
> >
> > We encountered a qmp-test ha
On Wed, Apr 04, 2018 at 02:53:46PM +0800, Peter Xu wrote:
> Free the AIO context earlier than the GMainContext (if we have) to
> workaround a possible Glib bug. No functional change at all.
>
> We encountered a qmp-test hang with oob:
>
> #0 0x7f35ffe45334 in __lll_lock_wait () from /lib6
On 04/04/2018 02:00 AM, Fam Zheng wrote:
> On Wed, 04/04 14:53, Peter Xu wrote:
>> Free the AIO context earlier than the GMainContext (if we have) to
>> workaround a possible Glib bug. No functional change at all.
>>
>>
>> With glib version 2.28.8-9 (current default version on centos6) we might
>
On Wed, 04/04 14:53, Peter Xu wrote:
> Free the AIO context earlier than the GMainContext (if we have) to
> workaround a possible Glib bug. No functional change at all.
>
> We encountered a qmp-test hang with oob:
>
> #0 0x7f35ffe45334 in __lll_lock_wait () from /lib64/libpthread.so.0
>
Free the AIO context earlier than the GMainContext (if we have) to
workaround a possible Glib bug. No functional change at all.
We encountered a qmp-test hang with oob:
#0 0x7f35ffe45334 in __lll_lock_wait () from /lib64/libpthread.so.0
#1 0x7f35ffe405d8 in _L_lock_854 () from /lib