| commit | 8857a1abeb4572aa5237d0461165e983e01da707 | |
| author | Matt Mackall <mpm@selenic.com> | |
| Fri, 29 Jan 2010 08:50:36 +0000 (29 21:50 +1300) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Tue, 9 Feb 2010 12:50:58 +0000 (9 04:50 -0800) | ||
| tree | 2301cf3b7efa990329229e9c3bc32a6e7fa6a932 | treesnapshot (tar.gz zip) |
| parent | 94af44b66b66bf9c848f11dc12fcd1558e55f995 | commitdiff |
random: drop weird m_time/a_time manipulation
commit a996996dd75a9086b12d1cb4010f26e1748993f0 upstream.
No other driver does anything remotely like this that I know of except
for the tty drivers, and I can't see any reason for random/urandom to do
it. In fact, it's a (trivial, harmless) timing information leak. And
obviously, it generates power- and flash-cycle wasting I/O, especially
if combined with something like hwrngd. Also, it breaks ubifs's
expectations.
Signed-off-by: Matt Mackall <mpm@selenic.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit a996996dd75a9086b12d1cb4010f26e1748993f0 upstream.
No other driver does anything remotely like this that I know of except
for the tty drivers, and I can't see any reason for random/urandom to do
it. In fact, it's a (trivial, harmless) timing information leak. And
obviously, it generates power- and flash-cycle wasting I/O, especially
if combined with something like hwrngd. Also, it breaks ubifs's
expectations.
Signed-off-by: Matt Mackall <mpm@selenic.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/char/random.c | diffblobblamehistory |