Bug 1746928
Summary: | glibc: Avoid fork handler lock for async-signal-safe fork | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Florian Weimer <fweimer> |
Component: | glibc | Assignee: | DJ Delorie <dj> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs |
Severity: | medium | Docs Contact: | Zuzana Zoubkova <zzoubkov> |
Priority: | medium | ||
Version: | 8.2 | CC: | ashankar, codonell, dj, fweimer, mnewsome, pfrankli, skolosov |
Target Milestone: | rc | Keywords: | Patch, Triaged |
Target Release: | 8.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glibc-2.28-83 | Doc Type: | Bug Fix |
Doc Text: |
.The `fork` function avoids certain deadlocks related to use of `pthread_atfork`
Previously, if a program registered an `atfork` handler and invoked `fork` from an asynchronous-signal handler, a defect in the internal implementation-dependent lock could cause the program to freeze. With this update, the implementation of `fork` and its `atfork` handlers is adjusted to avoid the deadlock in single-threaded programs.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 16:50:14 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: | |||
Bug Blocks: | 1746918 |
Description
Florian Weimer
2019-08-29 14:16:22 UTC
Please also verify upstream branch backports: release/2.30/master - May be required. Please check. release/2.29/master - May be required. Please check. release/2.28/master - May be required. Please check. Verified manually with gdb and a simplified test case based on tst-mallocfork2. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1828 |