Re: [PATCH v2] kdb: use ktime_get_mono_fast_ns() instead of ktime_get_ts()

From: Jason Wessel
Date: Tue Jan 30 2018 - 09:02:43 EST


On 01/30/2018 07:35 AM, Arnd Bergmann wrote:
On Mon, Jan 29, 2018 at 3:22 AM, Baolin Wang <baolin.wang@xxxxxxxxxx> wrote:
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 <baolin.wang@xxxxxxxxxx>

Reviewed-by: Arnd Bergmann <arnd@xxxxxxxx>



I'll add this in today, run some tests and it should be in the merge window.

Thanks,
Jason