Baolin Wang 40b90efeae kdb: use ktime_get_mono_fast_ns() instead of ktime_get_ts() ...

The kdb code will print the monotonic time by ktime_get_ts(), but
the ktime_get_ts() will be protected by a sequence lock, that will
introduce one deadlock risk if the lock was already held in the
context from which we entered the debugger.

Thus we can use the ktime_get_mono_fast_ns() to get the monotonic
time, which is NMI safe access to clock monotonic. Moreover we can
remove the 'struct timespec', which is not y2038 safe.

Signed-off-by: Baolin Wang <[email protected]>
Reviewed-by: Daniel Thompson <[email protected]>
Reviewed-by: Arnd Bergmann <[email protected]>
Signed-off-by: Jason Wessel <[email protected]>

2018-01-31 21:31:09 -06:00

..

kdb

kdb: use ktime_get_mono_fast_ns() instead of ktime_get_ts()

2018-01-31 21:31:09 -06:00

debug_core.c

sched/headers: Prepare for new header dependencies before moving code to <linux/sched/nmi.h>

2017-03-02 08:42:30 +01:00

debug_core.h

kgdb/kdb: Fix no KDB config problem

2014-01-25 08:55:09 +01:00

gdbstub.c

sched/headers: Prepare for new header dependencies before moving code to <linux/sched/signal.h>

2017-03-02 08:42:29 +01:00

Makefile

…