This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/13699] New: Hang in __lll_lock_wait_private after fork and realloc.
- From: "gf at unixsol dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 16 Feb 2012 11:36:07 +0000
- Subject: [Bug libc/13699] New: Hang in __lll_lock_wait_private after fork and realloc.
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13699
Bug #: 13699
Summary: Hang in __lll_lock_wait_private after fork and
realloc.
Product: glibc
Version: 2.13
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper.fsp@gmail.com
ReportedBy: gf@unixsol.org
Classification: Unclassified
I'm using glibc 2.13 from Slackware 13.37 on x86-64. One of our local programs
hangs from time to time and I have kill -9 it. Today I was able to get core
file and get the following back trace.
#0 0x00007f3118abfa8e in __lll_lock_wait_private () from /lib64/libc.so.6
#1 0x00007f3118a49c75 in _L_lock_12271 () from /lib64/libc.so.6
#2 0x00007f3118a47efd in realloc () from /lib64/libc.so.6
#3 0x00007f3118a3b633 in vasprintf () from /lib64/libc.so.6
#4 0x00007f3118a1c238 in asprintf () from /lib64/libc.so.6
#5 0x00007f31189f7863 in __assert_fail () from /lib64/libc.so.6
#6 0x00007f3118d76366 in __reclaim_stacks () from /lib64/libpthread.so.0
#7 0x00007f3118a78a36 in fork () from /lib64/libc.so.6
#8 0x000000000040672d in do_notify (in=<value optimized out>) at
lib/inotify.c:39
#9 0x00007f3118d76d6b in start_thread () from /lib64/libpthread.so.0
#10 0x00007f3118ab045d in clone () from /lib64/libc.so.6
The program uses about 4G memory on machine with 16G and and 2.6.38.7 kernel.
The notify function looks like this:
https://github.com/gfto/tsdecrypt/blob/master/notify.c#L46
I understand the problem is some kind of malloc related deadlock but I have no
idea how to avoid or work around it. There is currently glibc 2.14.1 in
slackware-current, will updating to this version fix the problem?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.