From: "Guozihua (Scott)" <guozihua@huawei.com>
To: <linux-crypto@vger.kernel.org>
Cc: <luto@kernel.org>, <tytso@mit.edu>
Subject: Inquiry about the removal of flag O_NONBLOCK on /dev/random
Date: Thu, 14 Jul 2022 15:33:47 +0800 [thread overview]
Message-ID: <13e1fa9d-4df8-1a99-ca22-d9d655f2d023@huawei.com> (raw)
Hi Community,
Recently we noticed the removal of flag O_NONBLOCK on /dev/random by
commit 30c08efec888 ("random: make /dev/random be almost like
/dev/urandom"), it seems that some of the open_source packages e.g.
random_get_fd() of util-linux and __getrandom() of glibc. The man page
for random() is not updated either.
Would anyone please kindly provide some background knowledge of this
flag and it's removal? Thanks!
--
Best
GUO Zihua
next reply other threads:[~2022-07-14 7:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 7:33 Guozihua (Scott) [this message]
2022-07-18 8:52 ` Inquiry about the removal of flag O_NONBLOCK on /dev/random Guozihua (Scott)
2022-07-19 3:47 ` Eric Biggers
2022-07-19 8:06 ` Guozihua (Scott)
2022-07-19 11:01 ` Jason A. Donenfeld
2022-07-21 3:50 ` Guozihua (Scott)
2022-07-21 4:07 ` Eric Biggers
2022-07-21 6:44 ` Guozihua (Scott)
2022-07-21 6:50 ` Eric Biggers
2022-07-21 10:37 ` Jason A. Donenfeld
2022-07-21 11:30 ` Guozihua (Scott)
2022-07-26 7:43 ` Guozihua (Scott)
2022-07-26 11:08 ` Jason A. Donenfeld
2022-07-26 11:33 ` Guozihua (Scott)
2022-07-28 8:24 ` Guozihua (Scott)
2022-09-06 7:14 ` Guozihua (Scott)
2022-09-06 10:16 ` Jason A. Donenfeld
2022-09-07 13:03 ` Jason A. Donenfeld
2022-09-08 3:31 ` Guozihua (Scott)
2022-09-08 9:51 ` Jason A. Donenfeld
2022-09-08 10:40 ` Jason A. Donenfeld
2022-09-08 14:26 ` [PATCH] random: restore O_NONBLOCK support Jason A. Donenfeld
2022-09-19 10:27 ` Inquiry about the removal of flag O_NONBLOCK on /dev/random Guozihua (Scott)
2022-09-19 10:40 ` Jason A. Donenfeld
2022-09-19 10:45 ` Guozihua (Scott)
2022-07-21 11:09 ` Theodore Ts'o
2022-07-21 11:30 ` Guozihua (Scott)
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=13e1fa9d-4df8-1a99-ca22-d9d655f2d023@huawei.com \
--to=guozihua@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=luto@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