From: Ian Kent <raven@themaw.net>
To: Leonardo Chiquitto <leonardo.lists@gmail.com>
Cc: autofs <autofs@vger.kernel.org>
Subject: Re: Linking against libldap_r instead of libldap?
Date: Fri, 28 Jun 2013 14:31:00 +0800 [thread overview]
Message-ID: <1372401060.21110.6.camel@perseus.fritz.box> (raw)
In-Reply-To: <CAEySpB4wm76DEJE-752Qd=_vtEMMi_vzr=eGu7RfUaJmbVT2GQ@mail.gmail.com>
On Thu, 2013-06-27 at 22:42 -0300, Leonardo Chiquitto wrote:
> Hi,
>
> I'm investigating one segmentation fault report (multiple occurrences)
> in automount where the OpenSSL context (using LDAP with TLS) is
> clearly corrupted. Reading OpenSSL documentation I found that the
> the library needs to be correctly initialized in order to run in a multi-
> threaded environment. I also found that *only* the reentrant build of
> the OpenLDAP libraries (libldap_r) initialize openssl for multi-threading.
>
> By default (since commit 04dfd15590a) automount is linked against
> libldap (non-reentrant), but I failed to find the reason behind the change.
> Could you help me understand why it shouldn't be linked against
> libldap_r?
That was a long time ago, Jan 2008.
Sorry, I don't remember why I committed that change.
TBH I always thought the re-entrant version of the library should be
used so there must have been a case to justify not using it, I just
can't remember what it was.
Not a good change log entry either .....
Ian
next prev parent reply other threads:[~2013-06-28 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 1:42 Linking against libldap_r instead of libldap? Leonardo Chiquitto
2013-06-28 6:31 ` Ian Kent [this message]
2013-06-28 7:26 ` Ian Kent
2013-07-26 17:39 ` Leonardo Chiquitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1372401060.21110.6.camel@perseus.fritz.box \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=leonardo.lists@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.