You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Michael Park (JIRA)" <ji...@apache.org> on 2015/01/22 01:00:42 UTC
[jira] [Commented] (MESOS-1432) Atomically set close-on-exec where
possible.
[ https://issues.apache.org/jira/browse/MESOS-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286590#comment-14286590 ]
Michael Park commented on MESOS-1432:
-------------------------------------
https://reviews.apache.org/r/30109/
https://reviews.apache.org/r/30148/
https://reviews.apache.org/r/30149/
> Atomically set close-on-exec where possible.
> --------------------------------------------
>
> Key: MESOS-1432
> URL: https://issues.apache.org/jira/browse/MESOS-1432
> Project: Mesos
> Issue Type: Bug
> Components: technical debt
> Reporter: Benjamin Mahler
> Assignee: Michael Park
>
> In our multi-threaded code, there is a race between opening a file descriptor and setting close-on-exec on it: if a fork occurs between these operations then we have leaked the file descriptor to the child process.
> Some required reading:
> http://udrepper.livejournal.com/20407.html
> We should do an audit of all of our code to ensure we're doing avoiding this race where possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)