diff options
| author |   Jason A. Donenfeld <Jason@zx2c4.com> | 2022-04-08 18:03:13 +0200 |
|---|---|---|
| committer | Jason A. Donenfeld <Jason@zx2c4.com> | 2022-05-13 23:59:23 +0200 |
| commit | ff8a8f59c99f6a7c656387addc4d9f2247d75077 (patch) | |
| tree | b4b3899b772d8a4ed4403a607340d1e7c0aad518 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | mips: use fallback for random_get_entropy() instead of just c0 random (diff) | |
| download | linux-dev-ff8a8f59c99f6a7c656387addc4d9f2247d75077.tar.xz linux-dev-ff8a8f59c99f6a7c656387addc4d9f2247d75077.zip | |
arm: use fallback for random_get_entropy() instead of zero
In the event that random_get_entropy() can't access a cycle counter or
similar, falling back to returning 0 is really not the best we can do.
Instead, at least calling random_get_entropy_fallback() would be
preferable, because that always needs to return _something_, even
falling back to jiffies eventually. It's not as though
random_get_entropy_fallback() is super high precision or guaranteed to
be entropic, but basically anything that's not zero all the time is
better than returning zero all the time.
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions