Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Oct 2018 15:18:52 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 221700] lang/python??: subprocess does not use closefrom, calls close(2) hundreds of thousands of times
Message-ID:  <bug-221700-21822-Jw75xxsXI0@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221700-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-221700-21822@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221700

--- Comment #10 from Ed Maste <emaste@freebsd.org> ---
A twitter discussion referenced this PR and the question of
async-signal-saftiness of closefrom:
https://twitter.com/koobs/status/1046674765585367041

Note that closefrom is in sigaction(2)'s list of async-signal-safe function=
s,
in the "Base Interfaces not specified as async-signal safe by POSIX, but
planned to be:" section. These are interfaces that are async-signal-safe in
FreeBSD, are not currently required to be so by POSIX, but are expected to =
be
so in the future. That said, I am not sure why closefrom is in that list and
not 'Extension Interfaces' as POSIX does not specify closefrom.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221700-21822-Jw75xxsXI0>