From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: Eyal Itkin <eyal.itkin@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Update tcache double-free check
Date: Sun, 4 Oct 2020 15:41:36 -0400 [thread overview]
Message-ID: <94403f67-f4b9-50c9-0be2-38a06f7101d3@redhat.com> (raw)
In-Reply-To: <CAA=iMU+XZx3jYX7UOLoXUvfaea-APf9+QTE9kUGokv0U7owCFg@mail.gmail.com>
On 10/3/20 5:04 AM, Eyal Itkin wrote:
> Ping. Is there any update on this subject?
Not yet.
My queue is:
- DSO sorting patches.
- Tcache double-free
- nsswitch (again)
I've been blocked by other deliverables.
I've reviewed some other patches, but they are
easier to reason about and review ;-)
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-10-04 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 13:37 [PATCH] Update tcache double-free check Eyal Itkin via Libc-alpha
2020-07-24 21:05 ` Carlos O'Donell via Libc-alpha
2020-07-25 10:39 ` Eyal Itkin via Libc-alpha
2020-07-25 21:07 ` Carlos O'Donell via Libc-alpha
2020-08-10 13:07 ` Eyal Itkin via Libc-alpha
2020-08-10 13:12 ` Carlos O'Donell via Libc-alpha
2020-08-10 13:35 ` Eyal Itkin via Libc-alpha
2020-08-10 13:44 ` Carlos O'Donell via Libc-alpha
2021-07-02 7:24 ` Siddhesh Poyarekar
2021-07-02 7:57 ` Eyal Itkin via Libc-alpha
2021-07-02 8:45 ` Siddhesh Poyarekar
2020-08-26 20:40 ` Carlos O'Donell via Libc-alpha
2020-10-03 9:04 ` Eyal Itkin via Libc-alpha
2020-10-04 19:41 ` Carlos O'Donell via Libc-alpha [this message]
2020-10-14 13:44 ` Eyal Itkin via Libc-alpha
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=94403f67-f4b9-50c9-0be2-38a06f7101d3@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=carlos@redhat.com \
--cc=eyal.itkin@gmail.com \
--cc=fweimer@redhat.com \
/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).