mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lijun Tang (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MESOS-6092) Docker containerizer launch command may access a "Container" struct after it has been destroyed
Date Sun, 04 Sep 2016 19:40:21 GMT

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

Lijun Tang reassigned MESOS-6092:
---------------------------------

    Assignee: Lijun Tang

> 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
>            Assignee: Lijun Tang
>            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
(v6.3.4#6332)

Mime
View raw message