From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [suggestion] tcache double-free check
Date: Fri, 24 Jul 2020 09:29:42 -0300 [thread overview]
Message-ID: <6bbca5cd-a0df-2046-9602-f5c3b2c4b1f8@linaro.org> (raw)
In-Reply-To: <CAA=iMUKU-Z3E-1YVi-ELNWmksQO2-a71EJz=eM7n5u6mp=X+ow@mail.gmail.com>
On 23/07/2020 19:07, Eyal Itkin via Libc-alpha wrote:
> OK, in a few days I will send a patch that will use a direct call to
> getrandom so to init the key.
> As the function call may fail (maybe there won't be enough entropy),
> on failure it will default to the alternative suggestion of using
> "!tcache" instead of "tcache".
You could also get some entropy from random-bits.h, although I am not
sure if clock entropy is suffice for this specific case.
prev parent reply other threads:[~2020-07-24 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 6:40 Eyal Itkin
2020-07-21 2:44 ` Carlos O'Donell
2020-07-21 6:03 ` Florian Weimer
2020-07-23 2:35 ` Carlos O'Donell
2020-07-23 11:56 ` Adhemerval Zanella
2020-07-23 12:06 ` Florian Weimer
2020-07-23 21:26 ` Carlos O'Donell
2020-07-23 22:07 ` Eyal Itkin
2020-07-24 3:01 ` Carlos O'Donell
2020-07-24 12:29 ` Adhemerval Zanella [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6bbca5cd-a0df-2046-9602-f5c3b2c4b1f8@linaro.org \
--to=adhemerval.zanella@linaro.org \
--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).