[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:
---
Fix Version/s: 1.4.2
> 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.4.2, 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)
[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)
[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:
---
Priority: Major (was: Critical)
> 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.4.1
>
>
> 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)
[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
]
Jie Yu updated MESOS-8159:
--
Fix Version/s: 1.4.1
> 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
>Priority: Critical
> Fix For: 1.4.1
>
>
> 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)
[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
]
Jie Yu updated MESOS-8159:
--
Priority: Critical (was: Trivial)
> 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
>Priority: Critical
>
> 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)
