diff options
author | Petr Mladek <pmladek@suse.com> | 2016-12-14 18:05:58 -0500 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-12-14 19:04:08 -0500 |
commit | 34aaff40b42148b23dcde40152480e25c7d2d759 (patch) | |
tree | 796f3d19fb9e51e3f6bb73722dcae6e224a36d8f /kernel/debug | |
parent | d5d8d3d0d4adcc3aec6e2e0fb656165014a712b7 (diff) |
kdb: call vkdb_printf() from vprintk_default() only when wanted
kdb_trap_printk allows to pass normal printk() messages to kdb via
vkdb_printk(). For example, it is used to get backtrace using the
classic show_stack(), see kdb_show_stack().
vkdb_printf() tries to avoid a potential infinite loop by disabling the
trap. But this approach is racy, for example:
CPU1 CPU2
vkdb_printf()
// assume that kdb_trap_printk == 0
saved_trap_printk = kdb_trap_printk;
kdb_trap_printk = 0;
kdb_show_stack()
kdb_trap_printk++;
Problem1: Now, a nested printk() on CPU0 calls vkdb_printf()
even when it should have been disabled. It will not
cause a deadlock but...
// using the outdated saved value: 0
kdb_trap_printk = saved_trap_printk;
kdb_trap_printk--;
Problem2: Now, kdb_trap_printk == -1 and will stay like this.
It means that all messages will get passed to kdb from
now on.
This patch removes the racy saved_trap_printk handling. Instead, the
recursion is prevented by a check for the locked CPU.
The solution is still kind of racy. A non-related printk(), from
another process, might get trapped by vkdb_printf(). And the wanted
printk() might not get trapped because kdb_printf_cpu is assigned. But
this problem existed even with the original code.
A proper solution would be to get_cpu() before setting kdb_trap_printk
and trap messages only from this CPU. I am not sure if it is worth the
effort, though.
In fact, the race is very theoretical. When kdb is running any of the
commands that use kdb_trap_printk there is a single active CPU and the
other CPUs should be in a holding pen inside kgdb_cpu_enter().
The only time this is violated is when there is a timeout waiting for
the other CPUs to report to the holding pen.
Finally, note that the situation is a bit schizophrenic. vkdb_printf()
explicitly allows recursion but only from KDB code that calls
kdb_printf() directly. On the other hand, the generic printk()
recursion is not allowed because it might cause an infinite loop. This
is why we could not hide the decision inside vkdb_printf() easily.
Link: http://lkml.kernel.org/r/1480412276-16690-4-git-send-email-pmladek@suse.com
Signed-off-by: Petr Mladek <pmladek@suse.com>
Cc: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Jason Wessel <jason.wessel@windriver.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/debug')
-rw-r--r-- | kernel/debug/kdb/kdb_io.c | 9 |
1 files changed, 2 insertions, 7 deletions
diff --git a/kernel/debug/kdb/kdb_io.c b/kernel/debug/kdb/kdb_io.c index daa76154fb1b..e74be38245ad 100644 --- a/kernel/debug/kdb/kdb_io.c +++ b/kernel/debug/kdb/kdb_io.c | |||
@@ -30,6 +30,7 @@ | |||
30 | char kdb_prompt_str[CMD_BUFLEN]; | 30 | char kdb_prompt_str[CMD_BUFLEN]; |
31 | 31 | ||
32 | int kdb_trap_printk; | 32 | int kdb_trap_printk; |
33 | int kdb_printf_cpu = -1; | ||
33 | 34 | ||
34 | static int kgdb_transition_check(char *buffer) | 35 | static int kgdb_transition_check(char *buffer) |
35 | { | 36 | { |
@@ -554,24 +555,19 @@ int vkdb_printf(enum kdb_msgsrc src, const char *fmt, va_list ap) | |||
554 | int linecount; | 555 | int linecount; |
555 | int colcount; | 556 | int colcount; |
556 | int logging, saved_loglevel = 0; | 557 | int logging, saved_loglevel = 0; |
557 | int saved_trap_printk; | ||
558 | int retlen = 0; | 558 | int retlen = 0; |
559 | int fnd, len; | 559 | int fnd, len; |
560 | int this_cpu, old_cpu; | 560 | int this_cpu, old_cpu; |
561 | static int kdb_printf_cpu = -1; | ||
562 | char *cp, *cp2, *cphold = NULL, replaced_byte = ' '; | 561 | char *cp, *cp2, *cphold = NULL, replaced_byte = ' '; |
563 | char *moreprompt = "more> "; | 562 | char *moreprompt = "more> "; |
564 | struct console *c = console_drivers; | 563 | struct console *c = console_drivers; |
565 | unsigned long uninitialized_var(flags); | 564 | unsigned long uninitialized_var(flags); |
566 | 565 | ||
567 | local_irq_save(flags); | ||
568 | saved_trap_printk = kdb_trap_printk; | ||
569 | kdb_trap_printk = 0; | ||
570 | |||
571 | /* Serialize kdb_printf if multiple cpus try to write at once. | 566 | /* Serialize kdb_printf if multiple cpus try to write at once. |
572 | * But if any cpu goes recursive in kdb, just print the output, | 567 | * But if any cpu goes recursive in kdb, just print the output, |
573 | * even if it is interleaved with any other text. | 568 | * even if it is interleaved with any other text. |
574 | */ | 569 | */ |
570 | local_irq_save(flags); | ||
575 | this_cpu = smp_processor_id(); | 571 | this_cpu = smp_processor_id(); |
576 | for (;;) { | 572 | for (;;) { |
577 | old_cpu = cmpxchg(&kdb_printf_cpu, -1, this_cpu); | 573 | old_cpu = cmpxchg(&kdb_printf_cpu, -1, this_cpu); |
@@ -849,7 +845,6 @@ kdb_print_out: | |||
849 | console_loglevel = saved_loglevel; | 845 | console_loglevel = saved_loglevel; |
850 | /* kdb_printf_cpu locked the code above. */ | 846 | /* kdb_printf_cpu locked the code above. */ |
851 | smp_store_release(&kdb_printf_cpu, old_cpu); | 847 | smp_store_release(&kdb_printf_cpu, old_cpu); |
852 | kdb_trap_printk = saved_trap_printk; | ||
853 | local_irq_restore(flags); | 848 | local_irq_restore(flags); |
854 | return retlen; | 849 | return retlen; |
855 | } | 850 | } |