Kees Cook d55535232c random: move rand_initialize() earlier
Right now rand_initialize() is run as an early_initcall(), but it only
depends on timekeeping_init() (for mixing ktime_get_real() into the
pools). However, the call to boot_init_stack_canary() for stack canary
initialization runs earlier, which triggers a warning at boot:

random: get_random_bytes called from start_kernel+0x357/0x548 with crng_init=0

Instead, this moves rand_initialize() to after timekeeping_init(), and moves
canary initialization here as well.

Note that this warning may still remain for machines that do not have
UEFI RNG support (which initializes the RNG pools during setup_arch()),
or for x86 machines without RDRAND (or booting without "random.trust=on"
or CONFIG_RANDOM_TRUST_CPU=y).

Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2019-04-19 23:27:05 -04:00
..
2019-03-06 09:41:12 -08:00
2018-03-14 19:13:47 +01:00
2018-06-05 11:24:55 -07:00
2019-02-26 12:53:55 +01:00
2019-01-22 10:21:45 +01:00
2018-05-16 07:23:35 +02:00
2019-01-22 10:21:45 +01:00
2018-06-12 16:19:22 -07:00
2019-01-01 13:24:31 -08:00