From: Andreas Schwab <schwab@suse.de>
To: DJ Delorie <dj@redhat.com>
Cc: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] malloc: Check for large bin list corruption when inserting unsorted chunk
Date: Wed, 15 May 2019 17:50:30 +0200 [thread overview]
Message-ID: <mvma7fnn2d5.fsf@suse.de> (raw)
In-Reply-To: <xnftrpw4yg.fsf@greed.delorie.com> (DJ Delorie's message of "Thu, 14 Mar 2019 16:56:07 -0400")
This lacks a ChangeLog entry.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-05-15 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 16:13 [PATCH] malloc: Check for large bin list corruption when inserting unsorted chunk Adam Maris
2019-02-12 16:34 ` Adam Maris
2019-02-21 10:40 ` Adam Maris
2019-02-22 1:30 ` DJ Delorie
2019-03-06 12:09 ` Florian Weimer
2019-03-14 20:56 ` DJ Delorie
2019-05-15 15:50 ` Andreas Schwab [this message]
2019-05-15 16:12 ` DJ Delorie
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mvma7fnn2d5.fsf@suse.de \
--to=schwab@suse.de \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).