From: Steven Rostedt <rostedt@goodmis.org>
To: Petr Mladek <pmladek@suse.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
sergey.senozhatsky@gmail.com, Tejun Heo <tj@kernel.org>,
akpm@linux-foundation.org, Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH] print kdump kernel loaded status in stack dump
Date: Wed, 17 Jan 2018 10:48:44 -0500 [thread overview]
Message-ID: <20180117104844.7ae779d2@gandalf.local.home> (raw)
In-Reply-To: <20180117134217.6gjr5ep3g2ns2v3w@pathway.suse.cz>
On Wed, 17 Jan 2018 14:42:17 +0100
Petr Mladek <pmladek@suse.com> wrote:
> > kexec_crash_loaded is enough, we only care if kdump kernel being
> > loaded or not, nothing else, no matter how long it has been loaded.
> > In Fedora/RHEL a kdump service takes care of loading the kernel but
> > it runs after networking is ready. If people want to save
> > the vmcore to nfs/ssh then we need detect network and build the
> > initramfs. In the nfs/ssh case if some networking code panicked it
> > is possible that kdump service has not started, but sometimes bug
> > can not be easily reproduced thus nobody can know if kdump is active
> > or not.
>
> I see.
>
> > Since kexec_crash_loaded() is already in kexec souce code, and it
> > is the only thing need to know, do you think it is really necessary
> > to add a printk_kexec_info()? I can do it if you strongly suggest
> > to do so.
>
> No, the original approach is fine if it is really that simple ;-)
I have to ask. Why is dump_stack_print_info() in printk to begin with.
It seems to be an odd place to put it, and not something I would think
should be in the printk() subsystem anyway. Why is it not in
lib/dump_stack.c?
>
> > >
> > > Finally, the style of the other lines is:
> > >
> > > Name: details
> > >
> > > I would suggest to print something like:
> > >
> > > Kexec: details
> > >
> > > , where the details might be whether the image is loaded,
> > > whether the loaded kernel is being executed, and
> > > other kexec-related flags.
> >
> > Will do, it can be something like:
> > Kexec: kdump kernel loaded
>
> Looks good to me. With this message, I could give this
> patch even
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
>
> I could update the string when pushing into printk.git.
> I am just going to wait a bit for more feedback if any.
The patch looks fine to me.
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2018-01-17 15:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 4:50 [PATCH] print kdump kernel loaded status in stack dump Dave Young
2018-01-17 8:57 ` Petr Mladek
2018-01-17 12:32 ` Dave Young
2018-01-17 13:42 ` Petr Mladek
2018-01-17 15:48 ` Steven Rostedt [this message]
2018-01-18 1:57 ` Dave Young
2018-01-18 18:02 ` Andi Kleen
2018-01-18 18:57 ` Steven Rostedt
2018-01-19 4:47 ` Dave Young
2018-01-19 13:06 ` Petr Tesarik
2018-01-26 7:37 ` Dave Young
2018-01-26 12:17 ` Petr Mladek
2018-01-27 3:57 ` Dave Young
2018-01-19 5:45 ` Sergey Senozhatsky
2018-01-19 8:16 ` Dave Young
2018-01-19 8:28 ` Sergey Senozhatsky
2018-01-19 8:42 ` Dave Young
2018-01-19 9:46 ` Sergey Senozhatsky
2018-01-19 8:32 ` Sergey Senozhatsky
2018-01-19 16:16 ` Andi Kleen
2018-01-19 16:51 ` Petr Tesarik
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=20180117104844.7ae779d2@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@kernel.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