You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Sivaram Kannan (JIRA)" <ji...@apache.org> on 2018/06/13 15:13:00 UTC
[jira] [Commented] (MESOS-6092) Docker containerizer launch command
may access a "Container" struct after it has been destroyed
[ https://issues.apache.org/jira/browse/MESOS-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511281#comment-16511281 ]
Sivaram Kannan commented on MESOS-6092:
---------------------------------------
Hi [~greggomann],
Can I work on this ticket?
./Siva.
> Docker containerizer launch command may access a "Container" struct after it has been destroyed
> -----------------------------------------------------------------------------------------------
>
> Key: MESOS-6092
> URL: https://issues.apache.org/jira/browse/MESOS-6092
> Project: Mesos
> Issue Type: Bug
> Reporter: Joseph Wu
> Priority: Minor
> Labels: easyfix, newbie
>
> Per a comment in this review: https://reviews.apache.org/r/51391/#review146735
> There are two places in the Docker containerizer where we copy a {{Container*}} by reference into a continuation:
> * https://github.com/apache/mesos/blob/71179708650642e145f75e250bf6d6b3eaabb6c5/src/slave/containerizer/docker.cpp#L1192
> * https://github.com/apache/mesos/blob/71179708650642e145f75e250bf6d6b3eaabb6c5/src/slave/containerizer/docker.cpp#L1283
> If the container is destroyed in the mean time, then we will potentially segfault here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)