Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1678421

Summary:	glibc: pthread_create vs EPERM error and stack cleanup.
Product:	Red Hat Enterprise Linux 6	Reporter:	Paulo Andrade <pandrade>
Component:	glibc	Assignee:	glibc team <glibc-bugzilla>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-tools-bugs
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.10	CC:	amike, ashankar, codonell, dj, fweimer, glibc-bugzilla, mnewsome, pfrankli
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-26 17:30:38 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 Paulo Andrade 2019-02-18 17:49:35 UTC

If clone returns EPERM the stack is deallocated. After clone is
successful, glibc might return EPERM if it fails to scheduling policies
and/or attributes. On the later case, the thread stack is not released
(no call to __deallocate_stack).

  User wants to know a defined behaviour when pthread_create returns EPERM.

  If the kernel returns EPERM for the clone call, all data is deallocated?
If glibc returns EPERM on subsequent syscalls it would need to create the
thread detached and explicitly call pthread_detach?

Comment 2 Florian Weimer 2019-02-18 19:18:45 UTC

This is about this upstream bug:

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

There is currently no workaround (besides avoiding to trigger the error condition).

Comment 3 Carlos O'Donell 2019-02-26 17:30:38 UTC

Red Hat Enterprise Linux 6 is in Maintenance Support Phase 2, and as such will only consider urgent priority bug fixes. The severity of this bug does not meet these requirements and so will not be considered for fixing in RHEL 6.10. Given that there is no upstream change, and any change would also depend upon the pthread_t ownership patches, this becomes too risky to backport into RHEL 6.10. Therefore I'm going to mark this as CLOSED/WONTFIX. If the severity if this becomes urgent for the customer, please feel free to reopen the bug.