[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4140) chain overlay may leak resources and suffer from concurrency issues

On Thu, 2005-11-03 at 13:52 -0800, Howard Chu wrote:
> ando@sys-net.it wrote:
> > Full_Name: Pierangelo Masarati
> > Version: HEAD, re23
> > OS: irrelevant
> > URL: ftp://ftp.openldap.org/incoming/
> > Submission from: (NULL) (
> > Submitted by: ando
> >
> >
> > In some cases, the chain overlay uses an automatic ldapinfo structure, which is
> > a copy of the original one except for the url.  This results in (at least)
> > leaking connections in the connection tree; it may also result in a corrupted
> > AVL tree and even worse, because mutex locking occurs on copies of the mutexes
> > and so.
> >   
> Ugh. We need to separate out the per-URL info from the overall backend 
> configuration so we can safely manage multiple URLs in back-ldap.

As a quick workaround, we may simply place a mutex 'round the chain
overlay's response function, to serialize chaining, under the assumption
that chaining is not going to be running all times.

Other solutions would likely be much more invasive in back-ldap.


    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497