socket: use OpenSSL multi-threading interfaces

OpenSSL isn't thread-safe unless you register these locking and thread
ID functions.  Most often the crashes would occur around
X509_verify_cert, even though it's insane that the certificate parsing
functions wouldn't be thread-safe.  The bug for this was filed over
two years ago, but it didn't seem like a high priority because the bug
didn't bite anyone until it caused a spurious regression-test failure.
Ironically, that was on a test for a *different* spurious
regression-test failure, which I guess is just deserts for leaving
this on the to-do list so long.

This is a backport of 8830e90fa1b131057e4ee1742cb83d78102714c0
>   Change-Id: I2a6c0e9b361abf54efa10ffbbbe071404f82b0d9
>   BUG: 906763
>   Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
>   Reviewed-on: http://review.gluster.org/10075
>   Tested-by: Gluster Build System <jenkins@build.gluster.com>
>   Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
>   Reviewed-by: Vijay Bellur <vbellur@redhat.com>

Change-Id: I66de5f2830936ccc8d447fed6d1a83ebe7e93460
BUG: 1218167
Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
Reviewed-on: http://review.gluster.org/10591
Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

0 files changed, 0 insertions, 0 deletions