From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Feng Tang <feng.tang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH 2/2] panic: Enable to print out all printk msg in buffer
Date: Wed, 10 Apr 2019 10:59:26 +0900 [thread overview]
Message-ID: <20190410015926.GC26212@jagdpanzerIV> (raw)
In-Reply-To: <20190409141430.w2fulp7jnnthojrc@pathway.suse.cz>
On (04/09/19 16:14), Petr Mladek wrote:
> We should:
>
> + Flush the latest messages before we replay the log.
Do you mean the pending messages? When we replay the log we also should
print "header line" and panic-cpu backtrace. So we will print panic-cpu
oops twice
// from panic-cpu flush_on_panic
[header]
backtrace
[end of header]
// from console_replay
then all logbuf messages
and then the same header/backtrace one more time
[header]
backtrace]
[end of backtrace]
Is there any particular reason to flush pending messages before
we play the buffer? Replaying the logbuf can take some time, so
my guess would be that you want to print panic-cpu backtrace as
soon as possible. Is there something else?
[..]
> Then I would update cosole_unlock() with something like:
>
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 02ca827b8fac..14ef4e2431e7 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2386,21 +2386,32 @@ void console_unlock(void)
>
> for (;;) {
> struct printk_log *msg;
> + int reset_idx = 0;
> size_t ext_len = 0;
> - size_t len;
> + size_t len = 0;
>
> printk_safe_enter_irqsave(flags);
> raw_spin_lock(&logbuf_lock);
> +
> if (console_seq < log_first_seq) {
> len = sprintf(text,
> "** %llu printk messages dropped **\n",
> log_first_seq - console_seq);
>
> /* messages are gone, move to first one */
> + reset_idx = 1;
> + }
> +
> + if (console_replay) {
> + len += sprintf(text + len,
> + "Replaying the entire log:\n");
> + reset_idx = 1;
> + console_replay = 0;
> + }
> +
> + if (reset_idx) {
> console_seq = log_first_seq;
> console_idx = log_first_idx;
> - } else {
> - len = 0;
> }
The printing loop becomes a bit complex with one more state, I should
say; but can do. We handle exclusive consoles there, dropped messages,
panic reset. But I see what you are trying to do.
-ss
next prev parent reply other threads:[~2019-04-10 1:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 10:48 [PATCH 1/2] printk: Add an option to flush all messages on panic Feng Tang
2019-04-01 10:48 ` [PATCH 2/2] panic: Enable to print out all printk msg in buffer Feng Tang
2019-04-09 14:14 ` Petr Mladek
2019-04-10 1:59 ` Sergey Senozhatsky [this message]
2019-04-10 8:02 ` Petr Mladek
2019-04-10 8:16 ` Sergey Senozhatsky
2019-04-10 10:12 ` Feng Tang
2019-04-01 11:50 ` [PATCH 1/2] printk: Add an option to flush all messages on panic Mukesh Ojha
2019-04-02 2:47 ` Feng Tang
2019-04-02 2:14 ` Sergey Senozhatsky
2019-04-02 2:28 ` Feng Tang
2019-04-02 2:29 ` Sergey Senozhatsky
2019-04-09 13:41 ` Petr Mladek
2019-04-10 1:47 ` Sergey Senozhatsky
2019-04-10 2:21 ` Feng Tang
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=20190410015926.GC26212@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=feng.tang@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
/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