Issue 24924: _posixsubprocess.c: sysconf() might not be async-signal-safe

➜

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/69112

classification

Type:	Stage:
Title:	_posixsubprocess.c: sysconf() might not be async-signal-safe
Components:	Extension Modules	Versions:

process

Dependencies:	Superseder:
Status:	open	Resolution:
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.

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:20	admin	set	github: 69112
2015年08月24日 16:24:01	r.david.murray	set	nosy: + gregory.p.smith
2015年08月24日 15:25:11	jwilk	create

homepage