[Bug 1081734] Re: malloc hangs when ltp mallocstress is run repeatedly

[Launchpad Bug Tracker]

This bug was fixed in the package eglibc - 2.15-0ubuntu20.1

---------------
eglibc (2.15-0ubuntu20.1) quantal; urgency=low

  * Add patch ubuntu/local-disable-nscd-netgroup-caching.diff to
    disable netgroup caching in the default config (LP: #1068889)
  * Backport any/cvs-malloc-deadlock.diff from upstream to prevent
    glibc deadlocking in mallock arena retry paths (LP: #1081734)
  * Fix futex issue (BZ #13844), backport from 2.16 (LP: #1091186)
  * Drop patch any/local-disable-nscd-host-caching.diff, as this
    bug was apparently resolved upstream a while ago (LP: #613662)
  * Add patch any/cvs-ld-self-load.diff to restore ld.so's ability
    to load itself, a behaviour accidentally removed (LP: #1088677)
  * Drop dangling libnss_db.so symlink in libc6-dev (LP: #1088773)
 -- Adam Conrad <adconrad at ubuntu.com>   Sun, 27 Jan 2013 16:46:30 -0700

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1081734

Title:
  malloc hangs when ltp mallocstress is run repeatedly

Status in “eglibc” package in Ubuntu:
  Fix Released
Status in “eglibc” source package in Precise:
  Fix Released
Status in “eglibc” source package in Quantal:
  Fix Released

Bug description:
  [Impact / Justification]
  There's a malloc deadlock in glibc, easily reproduced by the mallocstress part of ltp, but otherwise tripped in regular usage here and there.  The upstream patch applied in this SRU resolves that.

  [Test Case]
  Run mallocstress repeatedly before and after upgrade and watch the deadlocks be less deadlocky.

  [Regression Potential]
  This has been tested quite extensively upstream and in 2.16 in raring, and seems to be a marked improvement with no one reporting any adverse effects, so should be fine.

  [Original Report]
  - malloc sleeps continously when the mallocstress application which part of ltp package is executed in a loop.
  - From gdb backtrace it appears to be for a futex to be released in libc code. This is deadlock in glibc

  There are some discussions going on for including this fix in next eglibc release.
  emails
  http://sourceware.org/ml/libc-alpha/2012-06/msg00648.html
  http://permalink.gmane.org/gmane.comp.lib.glibc.alpha/23397
  http://sourceware.org/ml/libc-alpha/2012-07/msg00027.html
  http://sourceware.org/ml/libc-alpha/2012-08/msg00163.html
  http://permalink.gmane.org/gmane.linux.redhat.fedora.extras.cvs/832985

  discussion in http://sourceware-org.1504.n7.nabble.com/BZ-13939
  -malloc-deadlock-td13648.html#none

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1081734/+subscriptions