Bug 1991001

Summary:	swbz#19329 - dl-tls.c assert failure at concurrent pthread_create and dlopen
Product:	Red Hat Enterprise Linux 8	Reporter:	Ryan Mullett <rmullett>
Component:	glibc	Assignee:	Florian Weimer <fweimer>
Status:	CLOSED ERRATA	QA Contact:	Sergey Kolosov <skolosov>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	ashankar, codonell, dj, fweimer, mnewsome, pfrankli, sipoyare
Target Milestone:	beta	Keywords:	Bugfix, Patch, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glibc-2.28-175.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-10 15:17:47 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:

Description Ryan Mullett 2021-08-06 18:58:45 UTC

Description of problem:

Requesting the fix from swbz#19329 - dl-tls.c assert failure at concurrent pthread_create and dlopen be pulled into RHEL 8. 

https://sourceware.org/bugzilla/show_bug.cgi?id=19329

Version-Release number of selected component (if applicable):
glibc-2.28-127.el8_3.2.x86_64

How reproducible:
Always

Additional info:
Fixes seem to be available in 2.34 based on the most recent comment on the sourceware bz. Requesting that they be pulled into RHEL 8

Comment 1 Carlos O'Donell 2021-08-09 16:51:56 UTC

Ryan,

Thanks for the bug submission.

The upstream changes are a group of changes that alter the parallelism and concurrency (P&C) of the loader handling of thread local storage. These changes are very new in upstream.

I would like to see these changes achieve more operational hours upstream, we already found a defect in the changes that required subsequent fixes (DTV gap reuse logic). P&C issues require millions of CPU hours to make sure we don't see any issues across hardware architectures.

I will review these changes as part of our RHEL 8.6.0 planning (estimated release early in 2022).

Comment 13 errata-xmlrpc 2022-05-10 15:17:47 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:2005