[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/15546] New: real_fopen does not set CLOEXEC in thread-safe
From: |
tromey at redhat dot com |
Subject: |
[Bug binutils/15546] New: real_fopen does not set CLOEXEC in thread-safe way |
Date: |
Tue, 28 May 2013 18:23:09 +0000 |
http://sourceware.org/bugzilla/show_bug.cgi?id=15546
Bug ID: 15546
Summary: real_fopen does not set CLOEXEC in thread-safe way
Product: binutils
Version: unspecified
Status: NEW
Severity: minor
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: tromey at redhat dot com
Right now, bfdio.c:real_fopen sets the CLOEXEC flag on
any files it opens. Howevere, there is a window
between opening the file and setting this flag, during
which another thread could fork and exec.
The best fix would be to use O_CLOEXEC, or the fopen "e"
modifier, on platforms that support it.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug binutils/15546] New: real_fopen does not set CLOEXEC in thread-safe way,
tromey at redhat dot com <=