[389-devel] Please review: Bug 571677 - Busy replica on consumers when directly deleting a replication conflict

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=571677

The problem is that a bepreop can attempt to lock an entry in the cache 
that has already been locked by the caller.  I noticed that the modrdn 
code does not lock the target entries in the cache until after the 
bepreops have been called.  So I did the same for mod and del, and it 
worked, but I just don't know what else this may effect.  Comments?

https://bugzilla.redhat.com/attachment.cgi?id=402171&action=diff

https://bugzilla.redhat.com/attachment.cgi?id=402171&action=edit
--
389-devel mailing list
389-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-devel

[Index of Archives]     [Fedora Directory Announce]     [Fedora Users]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Review]     [Fedora Art]     [Fedora Music]     [Fedora Packaging]     [CentOS]     [Fedora SELinux]     [Big List of Linux Books]     [KDE Users]     [Fedora Art]     [Fedora Docs]

  Powered by Linux