[PATCH v3 1/7] printk: report dropped messages on separate line

From: Alex Elder
Date: Fri Jul 18 2014 - 10:14:29 EST


It is possible for the log to be filled too quickly for the consoles
to be able to keep up. This is detected in console_unlock(), and
when it occurs, a message is printed on the console. When reviewing
some nearby code, Petr MlÃdek suggested it might be nicer if this
message were placed on a separate line. This patch implements that
suggestion.

Suggested-by: Petr MlÃdek <pmladek@xxxxxxx>
Signed-off-by: Alex Elder <elder@xxxxxxxxxx>
---
kernel/printk/printk.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 13e839d..bed8f09 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -2142,9 +2142,10 @@ again:
}

if (console_seq < log_first_seq) {
- len = sprintf(text, "** %u printk messages dropped ** ",
+ len = sprintf(text,
+ "%s** %llu printk messages dropped **\n",
+ (console_prev & LOG_CONT) ? "\n" : "",
(unsigned)(log_first_seq - console_seq));
-
/* messages are gone, move to first one */
console_seq = log_first_seq;
console_idx = log_first_idx;
--
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/