diff options
| author | Matt Mackall <mpm@selenic.com> | 2010-01-29 11:50:36 +0300 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2010-02-01 22:50:23 +0300 |
| commit | a996996dd75a9086b12d1cb4010f26e1748993f0 (patch) | |
| tree | 3a65c1d6636f24e3edc175b54fabfdfd1fed91ef /drivers/crypto | |
| parent | 92dcffb916d309aa01778bf8963a6932e4014d07 (diff) | |
| download | linux-a996996dd75a9086b12d1cb4010f26e1748993f0.tar.xz | |
random: drop weird m_time/a_time manipulation
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>
Diffstat (limited to 'drivers/crypto')
0 files changed, 0 insertions, 0 deletions