Return-Path: X-Original-To: apmail-mesos-dev-archive@www.apache.org Delivered-To: apmail-mesos-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B4FA1105DB for ; Thu, 29 May 2014 00:28:01 +0000 (UTC) Received: (qmail 50405 invoked by uid 500); 29 May 2014 00:28:01 -0000 Delivered-To: apmail-mesos-dev-archive@mesos.apache.org Received: (qmail 50350 invoked by uid 500); 29 May 2014 00:28:01 -0000 Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list dev@mesos.apache.org Received: (qmail 50341 invoked by uid 99); 29 May 2014 00:28:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 00:28:01 +0000 Date: Thu, 29 May 2014 00:28:01 +0000 (UTC) From: "Benjamin Mahler (JIRA)" To: dev@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (MESOS-1432) Atomically set close-on-exec where possible. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Benjamin Mahler created MESOS-1432: -------------------------------------- Summary: Atomically set close-on-exec where possible. Key: MESOS-1432 URL: https://issues.apache.org/jira/browse/MESOS-1432 Project: Mesos Issue Type: Bug Reporter: Benjamin Mahler 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.2#6252)