On 06/21/2018 04:15 PM, Tobin C. Harding wrote: > Currently printing [hashed] pointers requires enough entropy to be > available. Early in the boot sequence this may not be the case > resulting in a dummy string '(____ptrval____)' being printed. This > makes debugging the early boot sequence difficult. We can relax the > requirement to use cryptographically secure hashing during debugging. > This enables debugging while keeping development/production kernel > behaviour the same. > > If new command line option debug_boot_weak_hash is enabled use > cryptographically insecure hashing and hash pointer value immediately. > > Reviewed-by: Steven Rostedt (VMware) <[email protected]> > Signed-off-by: Tobin C. Harding <[email protected]>
Acked-by: Randy Dunlap <[email protected]> Thanks. > --- > Documentation/admin-guide/kernel-parameters.txt | 8 ++++++++ > lib/vsprintf.c | 17 +++++++++++++++++ > 2 files changed, 25 insertions(+) -- ~Randy
