ff8a8f59c9
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>
16 lines
431 B
C
16 lines
431 B
C
/* SPDX-License-Identifier: GPL-2.0-only */
|
|
/*
|
|
* arch/arm/include/asm/timex.h
|
|
*
|
|
* Copyright (C) 1997,1998 Russell King
|
|
*
|
|
* Architecture Specific TIME specifications
|
|
*/
|
|
#ifndef _ASMARM_TIMEX_H
|
|
#define _ASMARM_TIMEX_H
|
|
|
|
typedef unsigned long cycles_t;
|
|
#define get_cycles() ({ cycles_t c; read_current_timer(&c) ? 0 : c; })
|
|
#define random_get_entropy() (((unsigned long)get_cycles()) ?: random_get_entropy_fallback())
|
|
|
|
#endif
|