thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James E. King, III (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (THRIFT-4164) Core in TSSLSocket cleanupOpenSSL when destroying a mutex used by openssl
Date Tue, 04 Apr 2017 13:37:42 GMT

     [ https://issues.apache.org/jira/browse/THRIFT-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James E. King, III updated THRIFT-4164:
---------------------------------------
    Labels: breaking_change  (was: )

> Core in TSSLSocket cleanupOpenSSL when destroying a mutex used by openssl
> -------------------------------------------------------------------------
>
>                 Key: THRIFT-4164
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4164
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 0.10.0
>         Environment: Ubuntu 14.04, openssl (version 1.0.2k)
>            Reporter: James E. King, III
>            Assignee: James E. King, III
>            Priority: Critical
>              Labels: breaking_change
>             Fix For: 0.11.0
>
>
> In a project where thrift is used, i was investigating a core in an assertion in apache::thrift::concurrency::~Mutex
(pthread variety).  The mutex in question was one of the locking mutexes that thrift gives
to openssl.  The core occurred in TSSLSocket::cleanupOpenSSL() where the mutexes are destroyed
(on the last line).
> I suspect that we might be changing the locking callbacks too early in the cleanup process;
perhaps one of the other cleanup calls that follows it would have released a mutex in some
situations?  In any case, this needs to be investigated and I am assigning it to myself.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message