From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Feng Tang <feng.tang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Borislav Petkov <bp@suse.de>,
ying.huang@intel.com
Subject: Re: [PATCH v2] panic: add an option to replay all the printk message in buffer
Date: Thu, 18 Apr 2019 19:50:46 +0900 [thread overview]
Message-ID: <20190418105046.GA13459@jagdpanzerIV> (raw)
In-Reply-To: <20190418074552.x7bl7tr76dui64f5@pathway.suse.cz>
On (04/18/19 09:45), Petr Mladek wrote:
> The following functions are currently called from panic_print_sys_info():
>
> + show_state():
> printk(KERN_INFO
> " task PC stack pid father\n");
> + show_mem():
> printk("Mem-Info:\n");
>
> + sysrq_timer_list_show()
> no global header; but each section can be easily distinguished
> because there are several static strings that explains the
> content
>
> + debug_show_all_locks()
> pr_warn("\nShowing all locks held in the system:\n");
>
> + ftrace_dump():
> printk(KERN_TRACE "Dumping ftrace buffer:\n");
Oh, thanks.
> The person that enabled the debugging option might know what it did
> when it process the log the very same day. It might be less clear
> for others reading the log.
>
> Also it still might be convenient to find the beginning easily.
> Or it might help to orientate when several test runs
> (over night test) are squashed in a single file. I see
> such logs pretty often.
OK, well since we are talking here about serial log, then we probably
can just add printk("dump logbuf:\n"). It will appear before the
FLUSH_ALL output. Or we can just tweak panic code a bit - anything
panic_print_sys_info() prints can be "after" end of panic marker.
Basically, just move pr_emerg("---[ end Kernel panic...") a bit. I don't
quite understand why is it at the bottom - we don't always print end of
panic maker, e.g. when panic_timeout != 0. Not sure if this was
intentional.
---
diff --git a/kernel/panic.c b/kernel/panic.c
index 50eacfc9bc7e..1940a142c26e 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -282,6 +282,7 @@ void panic(const char *fmt, ...)
*/
debug_locks_off();
console_flush_on_panic(CONSOLE_FLUSH_PENDING);
+ pr_emerg("---[ end Kernel panic - not syncing: %s ]---\n", buf);
panic_print_sys_info();
@@ -331,7 +332,6 @@ void panic(const char *fmt, ...)
disabled_wait(caller);
}
#endif
- pr_emerg("---[ end Kernel panic - not syncing: %s ]---\n", buf);
/* Do not scroll important messages printed above */
suppress_printk = 1;
---
-ss
prev parent reply other threads:[~2019-04-18 10:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 15:37 [PATCH v2] panic: add an option to replay all the printk message in buffer Feng Tang
2019-04-17 4:19 ` Andrew Morton
2019-04-17 6:48 ` Feng Tang
2019-04-17 9:18 ` Petr Mladek
2019-04-17 9:46 ` Sergey Senozhatsky
2019-04-17 10:50 ` Sergey Senozhatsky
2019-04-17 12:24 ` Petr Mladek
2019-04-17 15:18 ` Feng Tang
2019-04-18 0:00 ` Sergey Senozhatsky
2019-04-18 7:45 ` Petr Mladek
2019-04-18 9:00 ` Feng Tang
2019-04-18 11:01 ` Petr Mladek
2019-04-19 2:08 ` Feng Tang
2019-04-18 10:50 ` Sergey Senozhatsky [this message]
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=20190418105046.GA13459@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 \
--cc=ying.huang@intel.com \
/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