> 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. > There is no need to document this... man read(2) ;-) > > Jeff Igmar - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- /dev/random probs in 2.4test(12-pre3) Matthew Kirkwood
- Re: /dev/random probs in 2.4test(12-pre3) H. Peter Anvin
- Re: /dev/random probs in 2.4test(12-pre3) Matthew Kirkwood
- Re: /dev/random probs in 2.4test(12-pre3) folkert
- Re: /dev/random probs in 2.4test(12-pre3) Matthew Kirkwood
- Re: /dev/random probs in 2.4test(12-pre3) Igmar Palsenberg
- Re: /dev/random probs in 2.4test(12-pre... Jeff Garzik
- Re: /dev/random probs in 2.4test(1... Igmar Palsenberg
- Re: /dev/random probs in 2.4te... David Ford
- Re: /dev/random probs in 2... Albert D. Cahalan
- Re: /dev/random probs in 2... Theodore Y. Ts'o
- Re: /dev/random probs in 2... Alexander Viro
- Re: /dev/random probs in 2... Theodore Y. Ts'o
- Re: /dev/random probs in 2... Andrew Morton
- Re: /dev/random probs in 2... Igmar Palsenberg
- Re: /dev/random probs in 2... H. Peter Anvin
- Re: /dev/random probs in 2... Albert D. Cahalan
- Re: /dev/random probs in 2... Igmar Palsenberg