Backporting patches for #21754?
Florian Weimer
fweimer@redhat.com
Sun Jan 1 00:00:00 GMT 2017
On 11/20/2017 02:44 PM, Siddhesh Poyarekar wrote:
> Hi,
>
> The patch for #21754 changes the output on a heap corruption. That is,
> it no longer prints the backtrace when it detectes a heap corruption. I
> am considering backporting it because I want to backport Wilco's
> single-threaded improvements without change the code. Also, I reckon
> most distributions will want this patch backported anyway despite the
> user-visible change.
>
> Thoughts?
I don't see any problem with the backport.
Please be aware that if you backport
commit 24cffce7366c4070d8f823702a4fcec2cb732595
Author: Florian Weimer <fweimer@redhat.com>
Date: Thu Aug 31 14:55:11 2017 +0200
malloc: Resolve compilation failure in NDEBUG mode
you also need:
commit d74e6f6c0de55fc588b1ac09c88eb0fb8b8600af
Author: Wilco Dijkstra <wdijkstr@arm.com>
Date: Thu Oct 19 18:19:55 2017 +0100
Fix deadlock in _int_free consistency check
Thanks,
Florian
More information about the Libc-stable
mailing list