Bug 1422161 - glibc: fork is not async-signal-safe
Summary: glibc: fork is not async-signal-safe
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: 8.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: glibc team
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
: 1302896 (view as bug list)
Depends On: 1422159
Blocks: 1420851 1477664
TreeView+ depends on / blocked
 
Reported: 2017-02-14 15:48 UTC by Florian Weimer
Modified: 2023-07-18 14:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1422159
Environment:
Last Closed: 2020-02-24 14:48:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 2921161 0 None None None 2017-02-14 15:48:49 UTC
Sourceware 4737 0 P2 NEW fork is not async-signal-safe 2021-01-29 10:10:15 UTC

Description Florian Weimer 2017-02-14 15:48:50 UTC 
+++ This bug was initially created as a clone of Bug #1422159 +++

POSIX requires that fork is async-signal-safe.  Our current implementation is not.
Comment 2 Carlos O'Donell 2018-12-04 21:06:50 UTC 
*** Bug 1302896 has been marked as a duplicate of this bug. ***
Comment 4 Carlos O'Donell 2020-02-24 14:48:29 UTC 
We are going to track this bug upstream here:
"Bug 4737 - fork is not async-signal-safe"
https://sourceware.org/bugzilla/show_bug.cgi?id=4737

Significant improvements have been made upstream for the single-threaded case, making it AS-safe.

We are still not AS-safe for multi-threaded. That may be impossible to solve.
Note You need to log in before you can comment on or make changes to this bug.