public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "qboosh at pld-linux dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/770] New: possible deadlock on double-free logging
Date: Sat, 26 Feb 2005 21:29:00 -0000 [thread overview]
Message-ID: <20050226212906.770.qboosh@pld-linux.org> (raw)
_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=770
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-02-26 21:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 21:29 qboosh at pld-linux dot org [this message]
2005-02-26 21:35 ` [Bug libc/770] " qboosh at pld-linux dot org
2005-02-26 21:37 ` qboosh at pld-linux dot org
2005-02-26 21:38 ` qboosh at pld-linux dot org
2005-02-26 21:39 ` qboosh at pld-linux dot org
2008-04-30 20:28 ` bugzilla at tree dot tlrmx dot org
2010-06-01 1:50 ` pasky at suse dot cz
2010-06-01 15:19 ` bugzilla at tree dot tlrmx dot org
2010-06-01 16:11 ` pasky at suse dot cz
2010-06-01 18:34 ` bugzilla at tree dot tlrmx dot org
2010-09-17 4:48 ` matt at wilson dot org
2010-09-17 10:25 ` bugzilla at tree dot tlrmx dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050226212906.770.qboosh@pld-linux.org \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).