Bug 1527904
| Summary: | glibc: PTHREAD_STACK_MIN is too small on x86-64 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Florian Weimer <fweimer> |
| Component: | glibc | Assignee: | Carlos O'Donell <codonell> |
| Status: | CLOSED ERRATA | QA Contact: | Sergey Kolosov <skolosov> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.5 | CC: | ashankar, bgollahe, codonell, fweimer, lmiksik, mnewsome, pandrade, pfrankli, skolosov |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glibc-2.17-221.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Applications with PTHREAD_STACK_MIN sized thread stacks may experience segmentation faults as those threads run out of stack space. Such applications have incorrectly expected PTHREAD_STACK_MIN to provide enough stack space to do more than just start the thread. Applications should add to PTHREAD_STACK_MIN the stack required for their own uses. As an intermediate solution to allow existing applications to continue to operate the C runtime has been adjusted to use less stack space for key functionality. Existing applications should now continue to operate with PTHREAD_STACK_MIN sized thread stacks.
|
Story Points: | --- |
| Clone Of: | 1527887 | Environment: | |
| Last Closed: | 2018-04-10 14:04:32 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: | 1527905 | ||
| Bug Blocks: | |||
|
Description
Florian Weimer
2017-12-20 12:27:19 UTC
This is a regression introduced by glibc-2.17-196.el7_4.2 in <https://access.redhat.com/errata/RHBA-2017:3296>. *** Bug 1538776 has been marked as a duplicate of this bug. *** 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-2018:0805 |