History

printk/kdb: handle more message headers

Commit 4bcc595ccd80 ("printk: reinstate KERN_CONT for printing continuation lines") allows to define more message headers for a single message. The motivation is that continuous lines might get mixed. Therefore it make sense to define the right log level for every piece of a cont line. This patch introduces printk_skip_headers() that will skip all headers and uses it in the kdb code instead of printk_skip_level(). This approach helps to fix other printk_skip_level() users independently.

Petr Mladek committed 9 years ago

Commit 49795751 parent 22c2c7b2 files · +9 −1Browse files

Showing the changes to kernel/debug (1 of 2 files). Show all

Unified · Split

kernel/debug/kdb/kdb_io.c+1−1
@@ -697,7 +697,7 @@ kdb_printit: · 696 unmodified lines
697697 * Write to all consoles.
698698 */
699699 retlen = strlen(kdb_buffer);
700− cp = (char *) printk_skip_level(kdb_buffer);
700+ cp = (char *) printk_skip_headers(kdb_buffer);
701701 if (!dbg_kdb_mode && kgdb_connected) {
702702 gdbstub_msg_write(cp, retlen - (cp - kdb_buffer));
703703 } else {