Bug 188618 - concurrent access to /dev/urandom can output same value on smp kernels
concurrent access to /dev/urandom can output same value on smp kernels
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Don Howard
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-04-11 15:11 EDT by Marc Beauregard
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 14:45:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marc Beauregard 2006-04-11 15:11:11 EDT
Description of problem:
/dev/urandom can return duplicate values when two processors read from it at 
the same time.

Version-Release number of selected component (if applicable):

How reproducible:
Having 2 processes running on 2 processors accessing the /dev/urandom file.
Actual results:
The same values are read from the read() call on /dev/urandom.

Expected results:
Different values from the read() calls.

Additional info:
This bug has been fixed in kernel 2.6.10. When will this be introduced in the 
2.4.x kernels from RedHat ?

Do a search on 'concurrent acces /dev/urandom' and you should find the bug 
details and the bug fixes related to it.
Comment 1 RHEL Product and Program Management 2007-10-19 14:45:20 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.