m: libvir-list-boun...@redhat.com
> > > > [mailto:libvir-list-boun...@redhat.com]
> > > > On Behalf Of Michal Privoznik
> > > > Sent: Wednesday, April 04, 2018 5:21 PM
> > > > To: zhangzijian (Cloud); libvir-list@redhat.com
> > > > Cc: huangyong (Cloud)
>
st@redhat.com
>> Cc: huangyong (Cloud)
>> Subject: Re: [libvirt] hash: failed on concurrent iterating.
>>
>> On 04/04/2018 11:10 AM, Zhangzijian wrote:
>>> In function 'virHashForEach/virHashSearch', 'table->iterating' prevent
>> concurren
n Behalf Of Michal Privoznik
> > > Sent: Wednesday, April 04, 2018 5:21 PM
> > > To: zhangzijian (Cloud); libvir-list@redhat.com
> > > Cc: huangyong (Cloud)
> > > Subject: Re: [libvirt] hash: failed on concurrent iterating.
> > >
> > > On 04/04
angzijian (Cloud); libvir-list@redhat.com
> > Cc: huangyong (Cloud)
> > Subject: Re: [libvirt] hash: failed on concurrent iterating.
> >
> > On 04/04/2018 11:10 AM, Zhangzijian wrote:
> > > In function 'virHashForEach/virHashSearch', 'table->iterating
> -Original Message-
> From: libvir-list-boun...@redhat.com [mailto:libvir-list-boun...@redhat.com]
> On Behalf Of Michal Privoznik
> Sent: Wednesday, April 04, 2018 5:21 PM
> To: zhangzijian (Cloud); libvir-list@redhat.com
> Cc: huangyong (Cloud)
> Subject: Re: [lib
On 04/04/2018 11:10 AM, Zhangzijian wrote:
> In function 'virHashForEach/virHashSearch', 'table->iterating' prevent
> concurrent iterating. But most caller evoke it, after hold a read lock.
> This will lead the second caller failed to iterate the table. So, the caller
> should hold a write lock,
In function 'virHashForEach/virHashSearch', 'table->iterating' prevent
concurrent iterating. But most caller evoke it, after hold a read lock.
This will lead the second caller failed to iterate the table. So, the caller
should hold a write lock, then iterate the table.
--
libvir-list mailing lis