* Fwd: Re: [PATCH] malloc: Abort on heap corruption, without a backtrace [BZ #21754]
[not found] <CAKCAbMjeC2nK2+yNF48r5CDPRNoHJYi45fwweEZbiBZdF_KqWA@mail.gmail.com>
@ 2017-08-18 12:24 ` Florian Weimer
0 siblings, 0 replies; only message in thread
From: Florian Weimer @ 2017-08-18 12:24 UTC (permalink / raw)
To: GNU C Library
-------- 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-08-18 12:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CAKCAbMjeC2nK2+yNF48r5CDPRNoHJYi45fwweEZbiBZdF_KqWA@mail.gmail.com>
2017-08-18 12:24 ` Fwd: Re: [PATCH] malloc: Abort on heap corruption, without a backtrace [BZ #21754] Florian Weimer
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).