Re: [libvirt] [PATCH] storage_backend_rbd: always call rados_conf_read_file when connect a rbd pool

2017-01-18 Thread John Ferlan
[...] >> >> Could you provide a bit more context... >> >> Why does calling rados_conf_read_file with a NULL resolve the issue? >> >> Is this something "new" or "expected"? And if expected, why are we only >> seeing it now? >> >> What is the other thread that "has" the lock doing? > > It seams

Re: [libvirt] [PATCH] storage_backend_rbd: always call rados_conf_read_file when connect a rbd pool

2017-01-10 Thread Chen Hanxiao
At 2017-01-11 02:23:54, "John Ferlan" wrote: > > >On 12/30/2016 03:39 AM, Chen Hanxiao wrote: >> From: Chen Hanxiao >> >> This patch fix a dead lock when try to read a rbd image >> >> When trying to connect a rbd server >>

Re: [libvirt] [PATCH] storage_backend_rbd: always call rados_conf_read_file when connect a rbd pool

2017-01-10 Thread John Ferlan
On 12/30/2016 03:39 AM, Chen Hanxiao wrote: > From: Chen Hanxiao > > This patch fix a dead lock when try to read a rbd image > > When trying to connect a rbd server > (ceph-0.94.7-1.el7.centos.x86_64), > > rbd_list/rbd_open enter a dead lock state. > > Backtrace: >

[libvirt] [PATCH] storage_backend_rbd: always call rados_conf_read_file when connect a rbd pool

2016-12-30 Thread Chen Hanxiao
From: Chen Hanxiao This patch fix a dead lock when try to read a rbd image When trying to connect a rbd server (ceph-0.94.7-1.el7.centos.x86_64), rbd_list/rbd_open enter a dead lock state. Backtrace: Thread 30 (Thread 0x7fdb342d0700 (LWP 12105)): #0 0x7fdb40b16705