Bug 2091541 - glibc: Import bug fixes from glibc 2.34 upstream (snapshot 3) [rhel-9.1.0]
Summary: glibc: Import bug fixes from glibc 2.34 upstream (snapshot 3) [rhel-9.1.0]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: glibc
Version: 9.1
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Arjun Shankar
QA Contact: Sergey Kolosov
URL:
Whiteboard:
Depends On:
Blocks: 2073743 2080163 2091549
TreeView+ depends on / blocked
 
Reported: 2022-05-30 09:39 UTC by Arjun Shankar
Modified: 2023-07-18 14:29 UTC (History)
7 users (show)

Fixed In Version: glibc-2.34-38.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 11:11:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-123635 0 None None None 2022-05-30 09:42:54 UTC
Red Hat Product Errata RHBA-2022:8272 0 None None None 2022-11-15 11:12:26 UTC

Description Arjun Shankar 2022-05-30 09:39:38 UTC 
Import priority bug fixes from the glibc upstream 2.34 release branch.

The glibc upstream 2.34 branch is under active bug fix work and those fixes improve the quality of RHEL9.
Comment 1 Carlos O'Donell 2022-06-08 13:35:27 UTC 
This import will also fix the equivalent of bug 1888660 but for RHEL 9.1, fixing pthread_atfork handler deadlock.
Comment 4 Arjun Shankar 2022-06-14 13:28:44 UTC 
I synced f35 with release/2.34/master (and f36 with 2.35 to avoid regressions). All the necessary changes for this snapshot are now in f35.
Comment 8 errata-xmlrpc 2022-11-15 11:11:50 UTC 
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 (glibc bug fix and enhancement update), 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/RHBA-2022:8272
Note You need to log in before you can comment on or make changes to this bug.