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 6/7] printk: insert newline for truncated records
Date: Mon, 21 Jul 2014 09:27:49 -0500 [thread overview]
Message-ID: <53CD2365.4070707@linaro.org> (raw)
In-Reply-To: <20140721135703.GE20751@pathway.suse.cz>
On 07/21/2014 08:57 AM, Petr Mládek wrote:
> On Mon 2014-07-21 07:32:18, Alex Elder wrote:
>> On 07/21/2014 06:57 AM, Petr Mládek wrote:
>>> On Fri 2014-07-18 16:28:04, 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.
. . .
>>>> @@ -1023,9 +1029,13 @@ static size_t msg_print_text(const struct printk_log *msg, enum log_flags prev,
>>>>
>>>> if (buf) {
>>>> if (print_prefix(msg, syslog, NULL) +
>>>> - text_len + 1 >= size - len)
>>>> + text_len + 2 >= size - len)
>>>
>>> It counts the '\n' even when it is not used.
>>> I think that it is even wrong that it calculates prefix when it is not used.
>>
>> That's true, and I have yet another un-posted patch that
>> addresses this problem (well the second one). I am not
>> going to fix this problem in this patch, but the fix is
>> coming.
>>
>> Now that you're looking at the code I'm touching, you're
>> seeing the same things I did...
>>
>> I think I'll start posting that series later today or
>> tomorrow. I just hate to get too far ahead of myself.
>
> I suggest to always wait at least 24 hours before sending another
> version. I think that it is very hard for others to follow if there
> are too many versions in the wild and the code is too changing.
> This is why you get comments basically only from me.
Well, what I'm talking about would be a new series. But I'll
wait I guess.
FYI, here's what I have already posted:
- This series (v5 has now been posted)
- A "printk: more log flag simplification" series that
follows this one (had problems; will be reposted as
a truncated set)
And here are some things I have queued, but have not yet
posted for review:
- A patch that corrects the size calculation issue you
also noticed in msg_print_text().
- A series that I'm still verifying, which avoids formatting
all printk() messages repeatedly.
I will try to avoid having too many things out at once.
> Also a night usually helps to sort ideas and go the right direction.
> In fact, I was too fast myself as well. I am going to comment only one
> version per-day from now on :-)
Oh, all right. :)
>>>> break;
>>>>
>>>> + if (insert_newline) {
>>>> + insert_newline = false;
>>>> + buf[len++] = '\n';
>>>> + }
>>>> if (prefix)
>>>> len += print_prefix(msg, syslog, buf + len);
>>>> memcpy(buf + len, text, text_len);
. . .
>> Meanwhile, this patch is addressing essentially the same problem
>> in two spots, so I'd like to keep these together rather than
>> splitting it in two.
>
> I do not have strong opinion here.
I will keep it as I posted in v5. I moved this patch
earlier in the series, but did not combine it with the
first one.
>> I will move this patch earlier in the series, however, making
>> it follow patch 1.
>
> Sounds good.
Thanks for all your timely reviews, Petr.
-Alex
next prev parent reply other threads:[~2014-07-21 14:27 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
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 [this message]
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=53CD2365.4070707@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.