Bug 1313308
| Summary: | invalid fastbin entry (free), missing glibc patch | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Reznik <jreznik> |
| Component: | glibc | Assignee: | Carlos O'Donell <codonell> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.0 | CC: | ashankar, a.stimec, bkunal, codonell, cww, dkochuka, efi, fweimer, jkachuck, ken.verma, magoldma, mcermak, mnavrati, mnewsome, mpetlan, pfrankli, rcyriac, sumeet.keswani, tfrazier, trinh.dao, zpytela |
| Target Milestone: | rc | Keywords: | Patch, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glibc-2.17-106.el7_2.6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, certain code paths used by the C library's memory allocator "fastbins" feature, which were enabled by default, were not thread-safe. When the non-safe code paths executed, the code paths could cause corruption in the allocator, which cause the application terminate unexpectedly with a segmentation fault. The thread-unsafe code paths have been made thread-safe, and the described problem no longer occurs.
|
Story Points: | --- |
| Clone Of: | 1305406 | Environment: | |
| Last Closed: | 2016-05-12 09:59:37 UTC | Type: | --- |
| 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: | 1305406 | ||
| Bug Blocks: | 1097825 | ||
|
Description
Jaroslav Reznik
2016-03-01 11:23:23 UTC
Presence of the patch checked in glibc-2.17-106.el7_2.106 build tree. Since there is no reliable reproducer, we have to be content with SanityOnly here. 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://rhn.redhat.com/errata/RHBA-2016-1030.html |