[
https://issues.apache.org/jira/browse/MESOS-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bannier updated MESOS-6216:
------------------------------------
Attachment: build.log
Attached a trimmed build log showing a likely related issue,
https://builds.apache.org/job/Mesos/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-6)/2658/changes.
This build was configured with {{--enable-libevent --enable-ssl}} on centos-7.
> LibeventSSLSocketImpl::create is not thread-safe, but used as if it were
> ------------------------------------------------------------------------
>
> Key: MESOS-6216
> URL: https://issues.apache.org/jira/browse/MESOS-6216
> Project: Mesos
> Issue Type: Bug
> Components: security
> Reporter: Benjamin Bannier
> Attachments: build.log
>
>
> {{LibeventSSLSocketImpl::create}} is called whenever a potentially
> ssl-enabled socket is created. It in turn calls {{openssl::initialize}} which
> calls a function {{reinitialize}} using {{os::setenv}}. Here {{os::setenv}}
> is used to set up SSL-related libprocess environment variables
> {{LIBPROCESS_SSL_*}}.
> Since {{os::setenv}} is not thread-safe just like the {{::setenv}} it wraps,
> any code calling functions like {{os::getenv}} (via or {{os::environment}})
> concurrently with the first invocation of {{LibeventSSLSocketImpl::create}}
> perform unsynchronized r/w access to the same data structure in the runtime.
> We usually perform most setup of the environment before we start the
> libprocess runtime with {{process::initialize}} from a {{main}} function, see
> e.g., {{src/slave/main.cpp}} or {{src/master/main.cpp}} and others. It
> appears that we should move the setup of libprocess' SSL environment
> variables to a similar spot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
