From: Alex Elder <elder@linaro.org>
To: "Petr Mládek" <pmladek@suse.cz>
Cc: akpm@linux-foundation.org, kay@vrfy.org, bp@suse.de,
john.stultz@linaro.org, jack@suse.cz,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/7] printk: initialize syslog_prev and console_prev
Date: Mon, 21 Jul 2014 07:03:22 -0500 [thread overview]
Message-ID: <53CD018A.3080800@linaro.org> (raw)
In-Reply-To: <20140721100135.GB20751@pathway.suse.cz>
On 07/21/2014 05:01 AM, Petr Mládek wrote:
> On Fri 2014-07-18 16:28:00, Alex Elder wrote:
>> Two global variables, "syslog_prev" and "console_prev", maintain a
>> copy of the flags value used in the log record most recently
>> formatted for syslog or the console, respectively.
>>
>> Initially there is no previous formatted log record, and these
>> variables simply have an initial value 0. And occasionally log
>> records can get consumed at a rate such that syslog or the console
>> can't keep up, in which case those variables (along with their
>> corresponding position variables) must be reset. Here too, they're
>> reset to 0.
>>
>> This patch changes it so the initial value used is LOG_NEWLINE.
>> That is, if we know nothing about the prevously-formatted log
>> record, we can assume it was complete, and ended with a newline.
>>
>> This is being done to support the next patch. Initializing
>> these variables this way makes LOG_NEWLINE and LOG_CONT be
>> mutually exclusive, and the next patch uses that fact to simplify
>> some logic.
>
> I have decided to double check it and found more locations where the flags were
> reset to 0:
>
> + "prev" variable in syslog_print_all()
> + "prev" variable in kmsg_dump_get_buffer()
Yes, you're right. I'm glad you checked. Some of those
don't matter much (because they're only measuring the size
of the needed buffer) but I'll do it on all of them for
consistency.
> Also I think that we should not reset it to LOG_NEWLINE when the
> message is gone. I would suggest to do
>
> &= (LOG_CONT | LOG_NEWLINE);
What you're saying is that in the case we're resetting
because we couldn't keep up, we *do* in fact know something
about the previously-formatted message, so we should preserve
that. That's an astute observation. I like it, and will
implement it.
Thanks. v5 will be coming out this morning.
-Alex
> I mean to preserve the status of the last copied/printed piece. Then
> we could put there "\n" when the last proceed piece was continuous and
> the next one starts with prefix.
>
> The only exception would be "console_prev" in console_unlock()
> because there we already add "\n" in the "** %u printk messages
> dropped **" warning.
>
> How does that sound?
>
>
> Best Regards,
> Petr
>
>
>>
>> Signed-off-by: Alex Elder <elder@linaro.org>
>> Reviewed-by: Petr Mládek <pmladek@suse.cz>
>> ---
>> kernel/printk/printk.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
>> index ffc9928..4034a88 100644
>> --- a/kernel/printk/printk.c
>> +++ b/kernel/printk/printk.c
>> @@ -236,7 +236,7 @@ DECLARE_WAIT_QUEUE_HEAD(log_wait);
>> /* the next printk record to read by syslog(READ) or /proc/kmsg */
>> static u64 syslog_seq;
>> static u32 syslog_idx;
>> -static enum log_flags syslog_prev;
>> +static enum log_flags syslog_prev = LOG_NEWLINE;
>> static size_t syslog_partial;
>>
>> /* index and sequence number of the first record stored in the buffer */
>> @@ -250,7 +250,7 @@ static u32 log_next_idx;
>> /* the next printk record to write to the console */
>> static u64 console_seq;
>> static u32 console_idx;
>> -static enum log_flags console_prev;
>> +static enum log_flags console_prev = LOG_NEWLINE;
>>
>> /* the next printk record to read after the last 'clear' command */
>> static u64 clear_seq;
>> @@ -1071,7 +1071,7 @@ static int syslog_print(char __user *buf, int size)
>> /* messages are gone, move to first one */
>> syslog_seq = log_first_seq;
>> syslog_idx = log_first_idx;
>> - syslog_prev = 0;
>> + syslog_prev = LOG_NEWLINE;
>> syslog_partial = 0;
>> }
>> if (syslog_seq == log_next_seq) {
>> @@ -1301,7 +1301,7 @@ int do_syslog(int type, char __user *buf, int len, bool from_file)
>> /* messages are gone, move to first one */
>> syslog_seq = log_first_seq;
>> syslog_idx = log_first_idx;
>> - syslog_prev = 0;
>> + syslog_prev = LOG_NEWLINE;
>> syslog_partial = 0;
>> }
>> if (from_file) {
>> @@ -2149,7 +2149,7 @@ again:
>> /* messages are gone, move to first one */
>> console_seq = log_first_seq;
>> console_idx = log_first_idx;
>> - console_prev = 0;
>> + console_prev = LOG_NEWLINE;
>> } else {
>> len = 0;
>> }
>> --
>> 1.9.1
>>
next prev parent reply other threads:[~2014-07-21 12:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 21:27 [PATCH v4 0/7] printk: start simplifying some flags Alex Elder
2014-07-18 21:27 ` [PATCH v4 1/7] printk: report dropped messages on separate line Alex Elder
2014-07-21 9:39 ` Petr Mládek
2014-07-18 21:28 ` [PATCH v4 2/7] printk: initialize syslog_prev and console_prev Alex Elder
2014-07-21 10:01 ` Petr Mládek
2014-07-21 12:03 ` Alex Elder [this message]
2014-07-18 21:28 ` [PATCH v4 3/7] printk: LOG_CONT and LOG_NEWLINE are opposites Alex Elder
2014-07-18 21:28 ` [PATCH v4 4/7] printk: honor LOG_PREFIX in devkmsg_read() Alex Elder
2014-07-18 21:28 ` [PATCH v4 5/7] printk: honor LOG_PREFIX in msg_print_text() Alex Elder
2014-07-18 21:28 ` [PATCH v4 6/7] printk: insert newline for truncated records Alex Elder
2014-07-21 11:57 ` Petr Mládek
2014-07-21 12:32 ` Alex Elder
2014-07-21 13:57 ` Petr Mládek
2014-07-21 14:27 ` Alex Elder
2014-07-18 21:28 ` [PATCH v4 7/7] printk: correct some more typos 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=53CD018A.3080800@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.