From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: /dev/random probs in 2.4test(12-pre3)
Date: 19 Dec 2000 21:24:00 +0200 [thread overview]
Message-ID: <7sBg6EEXw-B@khms.westfalen.de> (raw)
In-Reply-To: <90cs2v$6u6$1@cesium.transmeta.com>
In-Reply-To: <90cs2v$6u6$1@cesium.transmeta.com>
hpa@zytor.com (H. Peter Anvin) wrote on 02.12.00 in <90cs2v$6u6$1@cesium.transmeta.com>:
> Again, that's wrong even when you replace /dev/random with something
> else. After all, you could be getting EINTR at any time, too, or get
> interrupted by a signal in the middle (in which case you'd get a short
> read.)
>
> SUCH CODE IS BROKEN. PERIOD. FULL STOP.
Well, one might argue that for some applications, it's sufficient to
detect and abort such a situation.
But not checking is *never* right. Except *maybe* for a throwaway program
whose source you erase after one use.
MfG Kai
-
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-19 21: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 [this message]
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
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=7sBg6EEXw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox