From: Till Smejkal <till.smejkal-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
beck-7YlrpqBBQ3VAfugRpC6u6w@public.gmane.org,
deraadt-VON6Tr2NNtkmbxgs1yVkuA@public.gmane.org,
Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>
Subject: Re: [PATCH -v4] random: introduce getrandom(2) system call
Date: Mon, 21 Jul 2014 22:21:26 +0200 [thread overview]
Message-ID: <20140721202125.GF1158@osiris> (raw)
In-Reply-To: <1405718127-30042-1-git-send-email-tytso-3s7WtUTddSA@public.gmane.org>
Hi,
On Fri, 18 Jul 2014, Theodore Ts'o wrote:
[...]
> If the GRND_RANDOM bit is not set, then the /dev/urandom pool
> will be used. Unlike using read(2) to fetch data from
> /dev/urandom, if the urandom pool has not been sufficiently
> initialized, getrandom(2) will block or return -1 with the
> errno set to EGAIN if the GRND_NONBLOCK bit is set in flags.
^^^^^
Small typo: this should be EAGAIN.
[...]
Regards
Till Smejkal
next prev parent reply other threads:[~2014-07-21 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 21:15 [PATCH -v4] random: introduce getrandom(2) system call Theodore Ts'o
[not found] ` <1405718127-30042-1-git-send-email-tytso-3s7WtUTddSA@public.gmane.org>
2014-07-21 20:21 ` Till Smejkal [this message]
2014-07-21 22:23 ` Theodore Ts'o
2014-07-22 14:36 ` Rolf Eike Beer
2014-07-30 12:26 ` Pavel Machek
2014-07-30 13:56 ` Bob Beck
2014-07-30 14:40 ` Bernd Petrovitsch
2014-07-30 22:18 ` Pavel Machek
2014-07-31 8:06 ` Bernd Petrovitsch
2014-08-03 11:38 ` Pavel Machek
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=20140721202125.GF1158@osiris \
--to=till.smejkal-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=beck-7YlrpqBBQ3VAfugRpC6u6w@public.gmane.org \
--cc=deraadt-VON6Tr2NNtkmbxgs1yVkuA@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).