kdb: Switch to nolock variants of kmsg_dump functions

The locked variants are prone to deadlocks (suppose we got to the
debugger w/ the logbuf lock held), so let's switch to nolock variants.

Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

authored by Anton Vorontsov and committed by Linus Torvalds c064da47 533827c9

Changed files
+4 -4
kernel
debug
+4 -4
kernel/debug/kdb/kdb_main.c
··· 2072 2072 kdb_set(2, setargs); 2073 2073 } 2074 2074 2075 - kmsg_dump_rewind(&dumper); 2076 - while (kmsg_dump_get_line(&dumper, 1, NULL, 0, NULL)) 2075 + kmsg_dump_rewind_nolock(&dumper); 2076 + while (kmsg_dump_get_line_nolock(&dumper, 1, NULL, 0, NULL)) 2077 2077 n++; 2078 2078 2079 2079 if (lines < 0) { ··· 2105 2105 if (skip >= n || skip < 0) 2106 2106 return 0; 2107 2107 2108 - kmsg_dump_rewind(&dumper); 2109 - while (kmsg_dump_get_line(&dumper, 1, buf, sizeof(buf), &len)) { 2108 + kmsg_dump_rewind_nolock(&dumper); 2109 + while (kmsg_dump_get_line_nolock(&dumper, 1, buf, sizeof(buf), &len)) { 2110 2110 if (skip) { 2111 2111 skip--; 2112 2112 continue;