linux

iv/linux

History

Jason A. Donenfeld 6d01238623 riscv: 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>
Cc: Paul Walmsley <paul.walmsley@sifive.com>
Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

2022-05-13 23:59:23 +02:00

boot

riscv: dts: microchip: reparent mpfs clocks

2022-04-22 18:40:30 -07:00

configs

RISC-V: configs: Configs that had RPMSG_CHAR now get RPMSG_CTRL

2022-04-26 08:19:53 -07:00

errata

riscv: errata: alternative: mark vendor_patch_func __initdata

2022-01-09 11:02:46 -08:00

include

riscv: use fallback for random_get_entropy() instead of zero