On 04/04/2018 11:50 AM, Zhangzijian wrote: >> -----Original Message----- >> From: libvir-list-bounces@xxxxxxxxxx [mailto:libvir-list-bounces@xxxxxxxxxx] >> On Behalf Of Michal Privoznik >> Sent: Wednesday, April 04, 2018 5:21 PM >> To: zhangzijian (Cloud); libvir-list@xxxxxxxxxx >> Cc: huangyong (Cloud) >> Subject: Re: hash: failed on concurrent iterating. >> >> 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, then iterate the table. >> >> Looks like there's another thread discussing this issue: >> > > Yes, the issue is still exist in v4.2.0. > Is it applicable to using write lock instead? Do you have a stack trace to share? Michal -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
