From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: getrandom syscall
Date: Wed, 28 Jan 2015 09:54:10 -0500 [thread overview]
Message-ID: <20150128145410.GH4574@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPLrYERojt8q5JDKG5UZJxoouKvN+OgAZz6ixhuFB85EPZzF6A@mail.gmail.com>
On Tue, Jan 27, 2015 at 11:12:46PM +0100, Daniel Cegiełka wrote:
> best regards,
> Daniel
Thanks. I've been wanting to get this added as well as a getentropy
function (the other API for the same thing).
> #include <stddef.h>
> #include <errno.h>
> #include "syscall.h"
>
> int getrandom(void *buf, size_t len)
> {
> int ret, pre_errno = errno;
There's no need to save/restore errno here. errno is only meaningful
after a function returns an error code. On success it should not be
inspected and could contain junk.
> if (len > 256) {
> errno = EIO;
> return -1;
> }
Could you explain the motivation for this part?
> do {
> ret = syscall(SYS_getrandom, buf, len, 0);
> } while (ret == -1 && errno == EINTR);
This would be more efficient (and avoid your errno issue entirely) if
you use __syscall which returns -errcode rather than storing errcode
in errno. It allows the whole loop to be inlined with no function
call. Something like:
while ((ret = __syscall(SYS_getrandom, buf, len, 0)) == -EINTR);
Of course there's the question of whether it should loop on EINTR
anyway; I don't know. Also if this can block there's the question of
whether it should be cancellable, but that can be decided later.
Finally, I wonder if it would make sense to use other fallbacks in the
case where the syscall is not supported -- perhaps the aux vector
AT_RANDOM or even /dev/urandom? (But I'd rather avoid doing anything
that depends on fds, which would make a function that appears to
always-work but actually fails on resource exhaustion.)
Rich
next prev parent reply other threads:[~2015-01-28 14:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 22:12 Daniel Cegiełka
2015-01-28 9:02 ` Szabolcs Nagy
2015-01-28 9:10 ` Daniel Cegiełka
2015-01-28 12:26 ` Szabolcs Nagy
2015-01-28 12:42 ` Daniel Cegiełka
2015-01-28 14:49 ` Rich Felker
2015-01-28 14:54 ` Rich Felker [this message]
2015-01-28 15:41 ` Szabolcs Nagy
2015-01-28 15:50 ` Daniel Cegiełka
2015-01-28 16:03 ` Szabolcs Nagy
2015-01-28 16:12 ` Daniel Cegiełka
2015-01-28 16:21 ` Rich Felker
2015-01-28 17:02 ` Daniel Cegiełka
2015-01-28 17:09 ` Daniel Cegiełka
2015-01-28 17:43 ` Brent Cook
2015-01-28 18:12 ` Daniel Cegiełka
2015-01-28 19:17 ` Rich Felker
2015-01-28 19:33 ` Daniel Cegiełka
2015-01-28 20:20 ` Brent Cook
2015-01-28 22:02 ` Rich Felker
2015-01-28 22:59 ` Josiah Worcester
2015-02-09 20:37 ` Andy Lutomirski
2015-01-28 16:25 ` Daniel Cegiełka
2015-01-28 16:01 ` Daniel Cegiełka
2015-01-28 15:41 ` Daniel Cegiełka
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=20150128145410.GH4574@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).