You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2017/11/15 19:32:00 UTC

[jira] [Updated] (MESOS-8159) ns::clone uses an async signal unsafe stack.

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

James Peach updated MESOS-8159:
-------------------------------
    Summary: ns::clone uses an async signal unsafe stack.  (was: ns::clone uses an async signal unsafe stack)

> ns::clone uses an async signal unsafe stack.
> --------------------------------------------
>
>                 Key: MESOS-8159
>                 URL: https://issues.apache.org/jira/browse/MESOS-8159
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 1.5.0
>
>
> In {{ns::clone}}, the first child call {{os::clone}} without passing a parameter for the stack. This causes {{os::clone}} to implicitly {{malloc}} a stack, which is not async-signal-safe.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)