From: Feng Tang <feng.tang@intel.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.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: Fri, 19 Apr 2019 10:08:35 +0800 [thread overview]
Message-ID: <20190419020835.xf6ccwdg3wfktwwl@shbuild888> (raw)
In-Reply-To: <20190418110152.szhc3rebqzgzrhjh@pathway.suse.cz>
On Thu, Apr 18, 2019 at 01:01:52PM +0200, Petr Mladek wrote:
> On Thu 2019-04-18 17:00:44, Feng Tang wrote:
> > Hi Petr,
> >
> > On Thu, Apr 18, 2019 at 09:45:52AM +0200, Petr Mladek wrote:
> > > On Thu 2019-04-18 09:00:14, Sergey Senozhatsky wrote:
> > > > I think that PANIC_PRINT_ALL_PRINTK_MSG is a debugging option; a quite
> > > > specific one. So people who ask the kernel to PANIC_PRINT_ALL_PRINTK_MSG
> > > > they know what they are doing, and we probably will not cofuse anyone.
> > > > After all, we don't print any headers when we ftrace_dump() or imitate
> > > > sysrq via sysrq_timer_list_show(), or for any other panic_print_sys_info()
> > > > printouts. So it's OK to just do the simple thing for
> > > > PANIC_PRINT_ALL_PRINTK_MSG.
> > >
> > > 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");
> > >
> > >
> > > 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.
> >
> > Thanks for checking all the info. For the note, how about adding
> > something like this inside panic_print_sys_info()?
> >
> > if (panic_print & PANIC_PRINT_ALL_PRINTK_MSG) {
> > printk("\nprintk: will replay all the messages in buffer:\n");
> > console_flush_on_panic(CONSOLE_FLUSH_ALL);
> > }
>
> This will store the message at the end of the buffer. It will repeat
> the message once again when replaying the log. I personally think
> that it is worse than printing nothing.
Got it :)
>
>
> > If you are all fine with it, I'll go post a v3, thanks,
>
> I suggest to wait few days. We might get opinion from someone
> else...
>
> Then sent whatever approach makes most sense to you. In fact, you
> are the 3rd person in this triangle. I believe that we will
> respect it. Last many mails are just a bike shedding.
>
> Just one thing. Please, use "replay" in the function or parameter
> name. The effect of console_flush_on_panic(CONSOLE_FLUSH_ALL)
> is really hard to guess from the name.
Ok. thanks
- Feng
next prev parent reply other threads:[~2019-04-19 2:05 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 [this message]
2019-04-18 10:50 ` Sergey Senozhatsky
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=20190419020835.xf6ccwdg3wfktwwl@shbuild888 \
--to=feng.tang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).