[Date Prev][Date Next]
Re: (ITS#6798) Mutex starvation on two-level referral for SASL connection
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#6798) Mutex starvation on two-level referral for SASL connection
- From: email@example.com
- Date: Thu, 11 May 2017 07:56:32 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
On Wed, May 10, 2017 at 01:19:50PM -0400, Stephen Gallagher wrote:
> On 05/10/2017 01:13 PM, Quanah Gibson-Mount wrote:
> > --On Wednesday, May 10, 2017 2:09 PM -0400 Stephen Gallagher
> > <firstname.lastname@example.org> wrote:
> >> Sorry, I'm not sure why you're directing this at me? I've not been
> >> involved with this bug at all.
> > Hi Stephen,
> > I'm not sure what you mean by "not involved". You are the one who
> > filed the bug report with us. Here is a direct link for a refresher:
> > <http://www.openldap.org/its/index.cgi/?findid=6798>
> In your previous email, you sent me the ITS number 8648. I missed that
> this was in reference to 6798 which I filed in 2011.
> I'm not sure if we still have a reproducer; I think we gave up years ago
> on using the built-in referral tracking of libldap. I'm CCing Jakub
> Hrozek who is the current tech lead on SSSD to see if he can still
> reproduce the issue.
I'm sorry, but I couldn't reproduce the issue any longer either. I remember
from some of RH customers that they were occasionally hitting this (or
similar?) issue and working around it by disabling the LDAP referral
chasing in SSSD but I couldn't reproduce now on demand, sorry.