Bug 1255822
Summary: | glibc: malloc may fall back to calling mmap prematurely if arenas are contended | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Siddhesh Poyarekar <spoyarek> | ||||
Component: | glibc | Assignee: | Carlos O'Donell <codonell> | ||||
Status: | CLOSED ERRATA | QA Contact: | Arjun Shankar <ashankar> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.3 | CC: | ashankar, fweimer, mcermak, mkolar, mnewsome, pfrankli | ||||
Target Milestone: | rc | Keywords: | Patch | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Cause:
In a low-memory situation, a logic error causes glibc malloc to use mmap even if memory is available internally without requesting it from the kernel.
Consequence:
The malloc implementation in glibc could use excessively rely on mmap, resulting performance problems.
Fix:
The logic error is corrected and available memory is reused.
Result:
Application performance in low-memory situations should improve.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 1348620 (view as bug list) | Environment: | |||||
Last Closed: | 2016-11-03 08:25:03 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: | 1348620 | ||||||
Bug Blocks: | 1297579, 1313485 | ||||||
Attachments: |
|
Description
Siddhesh Poyarekar
2015-08-21 16:00:41 UTC
Created attachment 1170318 [details]
glibc-rh1245731-4.patch
This is the patch which went into rhel-6.7.z.
Proposed upstream fix: https://sourceware.org/ml/libc-alpha/2016-06/msg00815.html Upstream commit: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=a3b473373ee43a292f5ec68a7fda6b9cfb26a9b0 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/RHSA-2016-2573.html |