[Date Prev][Date Next]
Re: derefDN locking problem (ITS#597)
> From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
> To: firstname.lastname@example.org
> At 06:56 PM 6/16/00 GMT, email@example.com wrote:
> >I found this bug by insert consistency checking in the RDWR code, e.g.
> >that the count of readers, writers, and waiters should never be negative.
> >The server immediately showed the error when doing ldapsearch with -a always.
> >Since I'm not sure what derefDN() is supposed to be doing, I'm at a lose
> >to fix it.
> I don't see this behavior in devel codes (though I've fixed a
> number of other aliasing problems). Likely need to carefully
> review the differences and backport key changes. Can
> you verify that I've added appropriate asserts to devel code
> to detect this? Also, we likely should add an alias test to
> our suite just to make sure we're both testing the same thing.
The assert()s in the dev code look good. The alias code in dev bears
very little resemblance to the 1.2 code. I exercised this bug in 1.2
with a sub-tree search for an entry that existed. The bug was
triggered during base analysis, not during the search. For my
production environment, I've disable alias dereferencing altogether,
since I'm not using any aliases.
Is alias support in LDAPv2 a UMICH extension? If so, I'd suggest
disabling it in the OpenLDAP 1.2 branch and not worrying about it.