This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/771] New: possible deadlock on double-free logging
- From: "qboosh at pld-linux dot org" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 26 Feb 2005 21:35:14 -0000
- Subject: [Bug libc/771] New: possible deadlock on double-free logging
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
_int_free() (malloc/malloc.c), which is called from free() with arena mutex
locked, checks and eventually prints/logs error message.
So if malloc_printerr() handling do some malloc()/free() on the same memory
arena, deadlock can occur.
vsyslog() can call free() during tz manipulation.
Yes, this deadlock is triggered by buggy code.
But it's all inside libc, not caused by actual memory corruption.
--
Summary: possible deadlock on double-free logging
Product: glibc
Version: 2.3.4
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: gotom at debian dot or dot jp
ReportedBy: qboosh at pld-linux dot org
CC: glibc-bugs at sources dot redhat dot com
http://sources.redhat.com/bugzilla/show_bug.cgi?id=771
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.