➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: _posixsubprocess.c: sysconf() might not be async-signal-safe
Type: Stage:
Components: Extension Modules Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: gregory.p.smith, jwilk
Priority: normal Keywords:

Created on 2015-08-24 15:25 by jwilk, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg249058 - (view) Author: Jakub Wilk (jwilk) Date: 2015-08-24 15:25 
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.
History
Date User Action Args
2022-04-11 14:58:20adminsetgithub: 69112
2015-08-24 16:24:01r.david.murraysetnosy: + gregory.p.smith
2015-08-24 15:25:11jwilkcreate