From: Florian Weimer <fweimer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Theodore Ts'o" <tytso-3s7WtUTddSA@public.gmane.org>,
Linux Kernel Developers List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
beck-7YlrpqBBQ3VAfugRpC6u6w@public.gmane.org
Subject: Re: [PATCH, RFC -v2] random: introduce getrandom(2) system call
Date: Fri, 18 Jul 2014 11:39:17 +0200 [thread overview]
Message-ID: <53C8EB45.20304@redhat.com> (raw)
In-Reply-To: <1405633100-4889-1-git-send-email-tytso-3s7WtUTddSA@public.gmane.org>
On 07/17/2014 11:38 PM, Theodore Ts'o wrote:
> If the GRND_RANDOM flags bit is set, then draw from the
> /dev/random pool instead of the /dev/urandom pool. The
> /dev/random pool is limited based on the entropy that can be
> obtained from environmental noise, so if there is insufficient
> entropy, the requested number of bytes may not be returned.
> If there is no entropy available at all, getrandom(2) will
> either block, or return an error with errno set to EAGAIN if
> the GRND_NONBLOCK bit is set in flags.
Can we get a GRND_INIT flag or something like that which means
"block/return EAGAIN until the kernel pool is initialized"? Thanks.
(See the previous discussion about pool initialization.)
--
Florian Weimer / Red Hat Product Security
next prev parent reply other threads:[~2014-07-18 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 21:38 [PATCH, RFC -v2] random: introduce getrandom(2) system call Theodore Ts'o
[not found] ` <1405633100-4889-1-git-send-email-tytso-3s7WtUTddSA@public.gmane.org>
2014-07-17 21:57 ` Zach Brown
2014-07-17 23:22 ` Theodore Ts'o
2014-07-18 9:39 ` Florian Weimer [this message]
[not found] ` <53C8EB45.20304-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-18 10:21 ` Theodore Ts'o
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=53C8EB45.20304@redhat.com \
--to=fweimer-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=beck-7YlrpqBBQ3VAfugRpC6u6w@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tytso-3s7WtUTddSA@public.gmane.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 NNTP newsgroup(s).