[issue24924] _posixsubprocess.c: sysconf() might not be async-signal-safe

[Jakub Wilk]

New submission from Jakub Wilk:

The safe_get_max_fd() (in Modules/_posixsubprocess.c) is documented to be async-signal-safe.

However, this function calls sysconf().
sysconf() was guaranteed to be async-singal-safe in SUSv3, but it's no longer in SUSv4.

I don't think it's going to be a problem in practice, but it's probably worth adding a clarification comment.

----------
components: Extension Modules
messages: 249058
nosy: jwilk
priority: normal
severity: normal
status: open
title: _posixsubprocess.c: sysconf() might not be async-signal-safe

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24924>
_______________________________________