Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1348000 - glibc: tst-malloc-usable spurious test failure
glibc: tst-malloc-usable spurious test failure
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: DJ Delorie
qe-baseos-tools
:
Depends On:
Blocks: 1473718
  Show dependency treegraph
 
Reported: 2016-06-19 16:56 EDT by Florian Weimer
Modified: 2018-04-10 09:57 EDT (History)
8 users (show)

See Also:
Fixed In Version: glibc-2.17-197.el7
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 09:56:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Sourceware 17581 None None None 2016-06-19 16:56 EDT
Red Hat Product Errata RHSA-2018:0805 None None None 2018-04-10 09:57 EDT

  None (edit)
Description Florian Weimer 2016-06-19 16:56:10 EDT
Occasionally, the test fails.  We need to backport this upstream change:

commit 265cbed8e73b23e3b38ada6cc42482c53a216224
Author: James Lemke <jwlemke@codesourcery.com>
Date:   Tue May 19 12:10:26 2015 -0700

    Fix for test "malloc_usable_size: expected 7 but got 11"
    
    [BZ #17581] The checking chain of unused chunks was terminated by a hash of
        the block pointer, which was sometimes confused with the chunk length byte.
        We now avoid using a length byte equal to the magic byte.


(NB: A first fix was reverted.)
Comment 8 errata-xmlrpc 2018-04-10 09:56:38 EDT
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

Note You need to log in before you can comment on or make changes to this bug.