This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Avoid deadlock in malloc on backtrace
- From: Florian Weimer <fweimer at redhat dot com>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: libc-alpha at sourceware dot org, carlos at redhat dot com
- Date: Tue, 24 Feb 2015 13:50:32 +0100
- Subject: Re: [PATCH] Avoid deadlock in malloc on backtrace
- Authentication-results: sourceware.org; auth=none
- References: <20150224100249 dot GA31871 at spoyarek dot pnq dot redhat dot com> <54EC52E6 dot 5010905 at redhat dot com> <20150224115158 dot GH23807 at spoyarek dot pnq dot redhat dot com> <54EC66CF dot 30800 at redhat dot com> <20150224120340 dot GI23807 at spoyarek dot pnq dot redhat dot com>
On 02/24/2015 01:03 PM, Siddhesh Poyarekar wrote:
> On Tue, Feb 24, 2015 at 12:55:59PM +0100, Florian Weimer wrote:
>> I think we should really consider removal. Most distributions will
>> have core dump catchers once they start using a glibc version derived
>> from master.
>
> I don't need a lot of convincing for this, but I guess we need more
> consensus. Does anybody think that removing the backtrace and maps is
> a bad idea?
Previous bugs filed for this:
https://sourceware.org/bugzilla/show_bug.cgi?id=12189 (CVE-2010-3192)
https://sourceware.org/bugzilla/show_bug.cgi?id=16159
The second bug appears to be the same thing you are fixing, Siddhesh.
--
Florian Weimer / Red Hat Product Security