From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
To: Stephan Mueller <smueller@chronox.de>
Cc: Alex Xu <alex_y_xu@yahoo.ca>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
virtualization@lists.linux-foundation.org
Subject: Re: getrandom waits for a long time when /dev/random is insufficiently read from
Date: Fri, 29 Jul 2016 12:24:27 +0200 [thread overview]
Message-ID: <CAJU7zaL8G28chcwEEYAquApm2ncPaBjKky4UPaWVy=6B+-rsCA@mail.gmail.com> (raw)
In-Reply-To: <2481163.nONN48TG9I@tauon.atsec.com>
On Fri, Jul 29, 2016 at 7:40 AM, Stephan Mueller <smueller@chronox.de> wrote:
> And finally, you have a coding error that is very very common but fatal when
> reading from /dev/random: you do not account for short reads which implies
> that your loop continues even in the case of short reads.
>
> Fix your code with something like the following:
> int read_random(char *buf, size_t buflen)
> {
> int fd = 0;
> ssize_t ret = 0;
> size_t len = 0;
>
> fd = open("/dev/random", O_RDONLY|O_CLOEXEC);
> if(0 > fd)
> return fd;
> do {
> ret = read(fd, (buf + len), (buflen - len));
> if (0 < ret)
> len += ret;
> } while ((0 < ret || EINTR == errno || ERESTART == errno)
> && buflen > len);
Unless there is a documentation error, the same is required when using
getrandom(). It can also return short as well as to be interrupted.
regards,
Nikos
next prev parent reply other threads:[~2016-07-29 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 22:07 getrandom waits for a long time when /dev/random is insufficiently read from Alex Xu
2016-07-29 5:40 ` Stephan Mueller
2016-07-29 10:24 ` Nikos Mavrogiannopoulos [this message]
2016-07-29 13:03 ` Alex Xu
2016-07-29 13:12 ` Stephan Mueller
2016-07-29 14:14 ` Alex Xu
2016-07-29 17:03 ` Stephan Mueller
2016-07-29 17:31 ` Alex Xu
2016-07-30 22:09 ` Theodore Ts'o
2016-07-31 1:53 ` Alex Xu via Virtualization
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='CAJU7zaL8G28chcwEEYAquApm2ncPaBjKky4UPaWVy=6B+-rsCA@mail.gmail.com' \
--to=nmav@gnutls.org \
--cc=alex_y_xu@yahoo.ca \
--cc=linux-crypto@vger.kernel.org \
--cc=smueller@chronox.de \
--cc=virtualization@lists.linux-foundation.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).