From: Theodore Ts'o Subject: Re: [PATCH -v4] random: introduce getrandom(2) system call Date: Mon, 21 Jul 2014 18:23:22 -0400 Message-ID: <20140721222322.GC24960@thunk.org> References: <1405718127-30042-1-git-send-email-tytso@mit.edu> <20140721202125.GF1158@osiris> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, beck-7YlrpqBBQ3VAfugRpC6u6w@public.gmane.org, deraadt-VON6Tr2NNtkmbxgs1yVkuA@public.gmane.org Return-path: Content-Disposition: inline In-Reply-To: <20140721202125.GF1158@osiris> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-crypto.vger.kernel.org On Mon, Jul 21, 2014 at 10:21:26PM +0200, Till Smejkal wrote: > 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. Thanks for pointing this out! Will fix. - Ted