From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: /dev/random probs in 2.4test(12-pre3)
Date: 2 Dec 2000 23:19:39 -0800 [thread overview]
Message-ID: <90cs6b$6uv$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1001202115753.27887T-100000@mandrakesoft.mandrakesoft.com> <Pine.LNX.4.21.0012022233440.11907-100000@server.serve.me.nl>
Followup to: <Pine.LNX.4.21.0012022233440.11907-100000@server.serve.me.nl>
By author: Igmar Palsenberg <maillist@chello.nl>
In newsgroup: linux.dev.kernel
>
> Hmm.. Some came to mind :
>
> Making /dev/random block if the amount requirements aren't met makes sense
> to me. If I request x bytes of random stuff, and get less, I probably
> reread /dev/random. If it's entropy pool is exhausted it makes sense to be
> to block.
>
Yes, it does, but it doesn't make any sense to block if there are data
to be read. If you need a larger read then you should advance your
pointer and try again with the residual size, or use fread() which
does this for you.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-03 7:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 17:33 /dev/random probs in 2.4test(12-pre3) folkert
2000-12-02 11:09 ` Matthew Kirkwood
2000-12-02 18:58 ` Igmar Palsenberg
2000-12-02 18:03 ` Jeff Garzik
2000-12-02 21:32 ` Igmar Palsenberg
2000-12-02 20:42 ` David Ford
2000-12-02 22:00 ` Albert D. Cahalan
2000-12-02 23:18 ` Theodore Y. Ts'o
2000-12-02 23:34 ` Alexander Viro
2000-12-03 3:01 ` Theodore Y. Ts'o
2000-12-03 12:20 ` Andrew Morton
2000-12-03 16:32 ` Igmar Palsenberg
2000-12-03 7:20 ` H. Peter Anvin
2000-12-03 7:41 ` Albert D. Cahalan
2000-12-03 16:25 ` Igmar Palsenberg
2000-12-03 18:52 ` Jeff Garzik
2000-12-03 21:18 ` Igmar Palsenberg
2000-12-03 20:15 ` David Ford
2000-12-03 7:17 ` H. Peter Anvin
2000-12-19 19:24 ` Kai Henningsen
2000-12-02 21:35 ` Igmar Palsenberg
2000-12-02 20:44 ` David Ford
2000-12-03 16:27 ` Igmar Palsenberg
2000-12-03 7:19 ` H. Peter Anvin [this message]
2000-12-03 7:16 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2000-12-01 17:26 Matthew Kirkwood
2000-12-01 18:18 ` H. Peter Anvin
2000-12-02 12:01 ` Matthew Kirkwood
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='90cs6b$6uv$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.