From: Carlos O'Donell <carlos@redhat.com>
To: Eyal Itkin <eyal.itkin@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [suggestion] tcache double-free check
Date: Thu, 23 Jul 2020 23:01:24 -0400 [thread overview]
Message-ID: <0d4519c5-dec1-83b2-3f78-21f1f0e2208b@redhat.com> (raw)
In-Reply-To: <CAA=iMUKU-Z3E-1YVi-ELNWmksQO2-a71EJz=eM7n5u6mp=X+ow@mail.gmail.com>
On 7/23/20 6:07 PM, Eyal Itkin 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".
That sounds good to me. Thanks.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-07-24 3:01 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 [this message]
2020-07-24 12:29 ` Adhemerval Zanella
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=0d4519c5-dec1-83b2-3f78-21f1f0e2208b@redhat.com \
--to=carlos@redhat.com \
--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).