Bug 1422161

Summary: glibc: fork is not async-signal-safe
Product: Red Hat Enterprise Linux 8 Reporter: Florian Weimer <fweimer>
Component: glibcAssignee: glibc team <glibc-bugzilla>
Status: CLOSED UPSTREAM QA Contact: qe-baseos-tools-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: ashankar, codonell, cww, dj, fweimer, mnewsome, pfrankli
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1422159 Environment:
Last Closed: 2020-02-24 14:48:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1422159    
Bug Blocks: 1420851, 1477664    

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.