From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
linux-api@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH -v5] random: introduce getrandom(2) system call
Date: Thu, 24 Jul 2014 12:18:14 -0300 [thread overview]
Message-ID: <20140724151814.GE32421@khazad-dum.debian.net> (raw)
In-Reply-To: <1406212287-9855-1-git-send-email-tytso@mit.edu>
On Thu, 24 Jul 2014, Theodore Ts'o wrote:
> ERRORS
> EINVAL An invalid flag was passed to getrandom(2)
>
> EFAULT buf is outside the accessible address space.
>
> EAGAIN The requested entropy was not available, and
> getentropy(2) would have blocked if GRND_BLOCK flag
> was set.
>
> EINTR While blocked waiting for entropy, the call was
> interrupted by a signal handler; see the description
> of how interrupted read(2) calls on "slow" devices
> are handled with and without the SA_RESTART flag
> in the signal(7) man page.
Should we add E<SOMETHING> to be able to deny access to GRND_RANDOM or some
future extension ?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2014-07-24 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 14:31 Theodore Ts'o
2014-07-24 15:18 ` Henrique de Moraes Holschuh [this message]
2014-07-24 15:21 ` Andy Lutomirski
2014-07-24 19:02 ` Theodore Ts'o
2014-07-24 20:30 ` Henrique de Moraes Holschuh
2014-07-24 20:54 ` Andy Lutomirski
2014-07-24 23:27 ` H. Peter Anvin
2014-07-24 23:24 ` Theodore Ts'o
2014-07-24 23:27 ` Andy Lutomirski
2014-07-25 13:22 ` Theodore Ts'o
2014-07-25 12:46 ` Henrique de Moraes Holschuh
2014-07-30 14:34 ` Rolf Eike Beer
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=20140724151814.GE32421@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®