Re: /dev/random probs in 2.4test(12-pre3)

["H. Peter Anvin" <hpa@zytor.com>]

Followup to:  <Pine.LNX.4.21.0012022229580.11907-100000@server.serve.me.nl>
By author:    Igmar Palsenberg <maillist@chello.nl>
In newsgroup: linux.dev.kernel
> 
> > For a blocking fd, read(2) has always blocked until some data is
> > available.  There has never been a guarantee, for any driver, that
> > a read(2) will return the full amount of bytes requested.
> 
> I know. Still leaves lot's of people that assume that reading /dev/random
> will return data, or will block.
> 
> I've seen lots of programs that will assume that if we request x bytes
> from /dev/random it will return x bytes.
> 

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.

	-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/