ando@OpenLDAP.org writes:
Modified Files: cache.c 1.32 -> 1.33 avoid potential deadlock?
I've never been sure of the back-monitor locking code.. Do volatile entries get cached?
Hallvard B Furuseth wrote:
ando@OpenLDAP.org writes:
Modified Files: cache.c 1.32 -> 1.33 avoid potential deadlock?
I've never been sure of the back-monitor locking code.. Do volatile entries get cached?
Of course not, as they're volatile.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati@sys-net.it ---------------------------------------
Pierangelo Masarati writes:
Hallvard B Furuseth wrote:
I've never been sure of the back-monitor locking code.. Do volatile entries get cached?
Of course not, as they're volatile.
Well, such entries are passed to monitor_cache_release(), that's when this potential deadlock could happen.
-
Hallvard B Furuseth -
Pierangelo Masarati