From: Siddhesh Poyarekar <siddhesh@gotplt.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: Fri, 2 Jul 2021 14:15:56 +0530 [thread overview]
Message-ID: <b3dcb849-8960-07e4-440e-1ec597edd15d@gotplt.org> (raw)
In-Reply-To: <CAA=iMU+DR8q1bcCQ=i=ALYp=+J1Ogp-z58664rCCaWjOAAWrcg@mail.gmail.com>
On 7/2/21 1:27 PM, Eyal Itkin wrote:
> Nice to see that this topic is still alive. As I said earlier,
> although my initial patch was per-thread, my later analysis convinced
> me that a per process solution will be a better idea.
>
> As for the benchmarking, the cost per-thread was negligible, so I
> don't see any potential risk with using the same solution (getrandom
> and all) just one time per process.
OK that's great, thanks for confirming.
> Sadly, I suggest you will modify my original patch / recreate a
> similar solution, as I can no longer commit new code to FSF. In the
> time passed the approval of my original employer has expired (approval
> was for a single year) and I also switched work place and will have to
> undergo the entire legal process yet again.
I understand.
> Given the maturity of the current draft, I suggest you will complete
> this feature based on my contribution (contribution that was made when
> it was still allowed). Without an additional similar feature in the
> near future, I don't see the benefit in troubling a VP for signing
> again the legal docs.
>
> Happy to see that this feature was not abandoned.
>
> Good luck to your all, and thanks for your enthusiasm for improving
> the security of such an important library.
No worries and thank you for sharing the idea and following up on it.
I'll post a draft soon.
Thanks,
Siddhesh
next prev parent reply other threads:[~2021-07-02 8:46 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 [this message]
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
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=b3dcb849-8960-07e4-440e-1ec597edd15d@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=eyal.itkin@gmail.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).