From: Alex Elder <elder@linaro.org>
To: akpm@linux-foundation.org
Cc: kay@vrfy.org, pmladek@suse.cz, bp@suse.de,
john.stultz@linaro.org, jack@suse.cz,
linux-kernel@vger.kernel.org
Subject: [PATCH v5 2/7] printk: insert newline for truncated records
Date: Mon, 21 Jul 2014 08:02:36 -0500 [thread overview]
Message-ID: <1405947761-26004-3-git-send-email-elder@linaro.org> (raw)
In-Reply-To: <1405947761-26004-1-git-send-email-elder@linaro.org>
If a log record has LOG_PREFIX set, its predecessor record should be
terminated if it was marked LOG_CONT.
In devkmsg_read(), this condition was being ignored, which would
lead to such records showing up combined when reading /dev/kmsg.
Fix this oversight.
We should similarly insert a newline in msg_print_text() in this
case, to avoid formatted records getting merged.
Suggested-by: Petr Mládek <pmladek@suse.cz>
Signed-off-by: Alex Elder <elder@linaro.org>
---
kernel/printk/printk.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index ffc9928..9f11eab 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -575,6 +575,7 @@ static ssize_t devkmsg_read(struct file *file, char __user *buf,
char cont = '-';
size_t len;
ssize_t ret;
+ bool insert_newline;
if (!user)
return -EBADF;
@@ -625,7 +626,10 @@ static ssize_t devkmsg_read(struct file *file, char __user *buf,
((user->prev & LOG_CONT) && !(msg->flags & LOG_PREFIX)))
cont = '+';
- len = sprintf(user->buf, "%u,%llu,%llu,%c;",
+ /* Insert a newline if the previous line was not terminated properly */
+ insert_newline = (user->prev & LOG_CONT) && (msg->flags & LOG_PREFIX);
+ len = sprintf(user->buf, "%s%u,%llu,%llu,%c;",
+ insert_newline ? "\n" : "",
(msg->facility << 3) | msg->level,
user->seq, ts_usec, cont);
user->prev = msg->flags;
@@ -1013,6 +1017,12 @@ static size_t msg_print_text(const struct printk_log *msg, enum log_flags prev,
newline = false;
}
+ if ((prev & LOG_CONT) && (msg->flags & LOG_PREFIX) && len < size) {
+ if (buf)
+ buf[len++] = '\n';
+ else
+ len++;
+ }
do {
const char *next = memchr(text, '\n', text_size);
size_t text_len;
--
1.9.1
next prev parent reply other threads:[~2014-07-21 13:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 13:02 [PATCH v5 0/7] printk: start simplifying some flags Alex Elder
2014-07-21 13:02 ` [PATCH v5 1/7] printk: report dropped messages on separate line Alex Elder
2014-07-21 13:02 ` Alex Elder [this message]
2014-07-22 9:45 ` [PATCH v5 2/7] printk: insert newline for truncated records Petr Mládek
2014-07-21 13:02 ` [PATCH v5 3/7] printk: initialize syslog_prev and console_prev Alex Elder
2014-07-22 11:48 ` Alex Elder
2014-07-22 12:01 ` Petr Mládek
2014-07-21 13:02 ` [PATCH v5 4/7] printk: LOG_CONT and LOG_NEWLINE are opposites Alex Elder
2014-07-21 13:02 ` [PATCH v5 5/7] printk: honor LOG_PREFIX in devkmsg_read() Alex Elder
2014-07-21 13:02 ` [PATCH v5 6/7] printk: honor LOG_PREFIX in msg_print_text() Alex Elder
2014-07-21 13:02 ` [PATCH v5 7/7] printk: correct some more typos Alex Elder
2014-07-22 10:04 ` [PATCH v5 0/7] printk: start simplifying some flags Petr Mládek
2014-07-22 11:23 ` Alex Elder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1405947761-26004-3-git-send-email-elder@linaro.org \
--to=elder@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=jack@suse.cz \
--cc=john.stultz@linaro.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome