c04e72700f
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> Acked-by: Dinh Nguyen <dinguyen@kernel.org> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
16 lines
367 B
C
16 lines
367 B
C
/* SPDX-License-Identifier: GPL-2.0-only */
|
|
/* Copyright Altera Corporation (C) 2014. All rights reserved.
|
|
*/
|
|
|
|
#ifndef _ASM_NIOS2_TIMEX_H
|
|
#define _ASM_NIOS2_TIMEX_H
|
|
|
|
typedef unsigned long cycles_t;
|
|
|
|
extern cycles_t get_cycles(void);
|
|
#define get_cycles get_cycles
|
|
|
|
#define random_get_entropy() (((unsigned long)get_cycles()) ?: random_get_entropy_fallback())
|
|
|
|
#endif
|