From: Alex Elder <elder@linaro.org>
To: "Petr Mládek" <pmladek@suse.cz>
Cc: akpm@linux-foundation.org, bp@suse.de, john.stultz@linaro.org,
jack@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/6] printk: insert newline in devkmsg_read()
Date: Fri, 18 Jul 2014 09:02:18 -0500 [thread overview]
Message-ID: <53C928EA.4000800@linaro.org> (raw)
In-Reply-To: <20140718114506.GA6774@pathway.suse.cz>
On 07/18/2014 06:45 AM, Petr Mládek wrote:
> On Thu 2014-07-17 09:09:10, Alex Elder wrote:
>> 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.
>>
>> Reported-by: Petr Mládek <pmladek@suse.cz>
>> Signed-off-by: Alex Elder <elder@linaro.org>
>> ---
>> kernel/printk/printk.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
>> index e5ee1cb..3174ba9 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;
>> @@ -626,7 +627,10 @@ static ssize_t devkmsg_read(struct file *file, char __user *buf,
>> else
>> cont = '-';
>>
>> - len = sprintf(user->buf, "%u,%llu,%llu,%c;",
>> + /* Insert a newline if we're terminating the previous record
>> early */
>
> More correct description would be:
>
> /* Insert a newline if the previous line was not terminated properly */
I will change it as you suggest.
>
>> + 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;
>
> Please, do similar change also in msg_print_text() that would fix also
> syslog(). Note that syslog is the place where we stopped to disable
> prefix when there was continuous line before.
I will do this, as you will see in v3 which I plan to post in a
few hours. (Note that this touches a spot where I have yet another
minor bug fix that I have not yet posted... Oh well.)
-Alex
> Best Regards.
> Petr
>
next prev parent reply other threads:[~2014-07-18 14:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 14:09 [PATCH v2 0/6] printk: start simplifying some flags Alex Elder
2014-07-17 14:09 ` [PATCH v2 1/6] printk: initialize syslog_prev and console_prev Alex Elder
2014-07-18 10:43 ` Petr Mládek
2014-07-18 13:38 ` Alex Elder
2014-07-17 14:09 ` [PATCH v2 2/6] printk: LOG_CONT and LOG_NEWLINE are opposites Alex Elder
2014-07-18 10:53 ` Petr Mládek
2014-07-18 13:39 ` Alex Elder
2014-07-17 14:09 ` [PATCH v2 3/6] printk: honor LOG_PREFIX in devkmsg_read() Alex Elder
2014-07-17 14:09 ` [PATCH v2 4/6] printk: honor LOG_PREFIX in msg_print_text() Alex Elder
2014-07-18 11:03 ` Petr Mládek
2014-07-17 14:09 ` [PATCH v2 5/6] printk: insert newline in devkmsg_read() Alex Elder
2014-07-18 11:45 ` Petr Mládek
2014-07-18 14:02 ` Alex Elder [this message]
2014-07-17 14:09 ` [PATCH v2 6/6] printk: correct some more typos Alex Elder
2014-07-18 11:46 ` Petr Mládek
2014-07-17 15:59 ` [PATCH v2 0/6] printk: start simplifying some flags Joe Perches
2014-07-17 16:04 ` 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=53C928EA.4000800@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=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