This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Fwd: Re: [PATCH] malloc: Abort on heap corruption, without a backtrace [BZ #21754]
- From: Florian Weimer <fweimer at redhat dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 18 Aug 2017 14:24:13 +0200
- Subject: Fwd: Re: [PATCH] malloc: Abort on heap corruption, without a backtrace [BZ #21754]
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx08.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx08.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=fweimer at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com ACC7FC0587E5
- References: <CAKCAbMjeC2nK2+yNF48r5CDPRNoHJYi45fwweEZbiBZdF_KqWA@mail.gmail.com>
-------- Forwarded Message --------
Subject: Re: [PATCH] malloc: Abort on heap corruption, without a
backtrace [BZ #21754]
Date: Fri, 18 Aug 2017 12:21:10 +0000
From: Zack Weinberg <zackw@panix.com>
To: Florian Weimer <fweimer@redhat.com>
On Fri, Aug 18, 2017 at 7:52 AM Florian Weimer <fweimer@redhat.com> wrote:
> I really think we should avoid generating backtraces on heap
> corruption. The process is in a precarious state at this point, and
> doing more work at this point risks obscuring the root cause of the
> corruption or enabling code execution exploits.
I am not familiar with this part of the code but I agree with this logic.
(Please forward to the list, I can't send plaintext email right now)
zw