From: ebiederm@xmission.com (Eric W. Biederman)
To: "河合英宏 / KAWAI,HIDEHIRO" <hidehiro.kawai.ez@hitachi.com>
Cc: "Vivek Goyal" <vgoyal@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"Baoquan He" <bhe@redhat.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"HATAYAMA Daisuke" <d.hatayama@jp.fujitsu.com>,
"平松雅巳 / HIRAMATU,MASAMI" <masami.hiramatsu.pt@hitachi.com>,
"Daniel Walker" <dwalker@fifo99.com>,
"Ingo Molnar" <mingo@kernel.org>
Subject: Re: [RFC V2 PATCH 0/1] kexec: crash_kexec_post_notifiers boot option related fixes
Date: Wed, 05 Aug 2015 12:10:06 -0500 [thread overview]
Message-ID: <87io8tvez5.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <04EAB7311EE43145B2D3536183D1A84454926993@GSjpTKYDCembx31.service.hitachi.net> ("河合英宏 / KAWAI,HIDEHIRO"'s message of "Tue, 4 Aug 2015 11:41:14 +0000")
"河合英宏 / KAWAI,HIDEHIRO" <hidehiro.kawai.ez@hitachi.com> writes:
> Hello,
>
> Thanks for the reply.
>
>> From: Eric W. Biederman [mailto:ebiederm@xmission.com]
> [...]
>> A specific hook for a very specific purpose when there is no other way
>> we can consider.
>
> So, is kmsg_dump like feature admissible?
>
>> If you don't have something that generalises well into a general purpose
>> operation that it makes sense for everyone to call you can always use
>> the world's largest aka you can run code before the new kernel starts
>> that is loaded with kexec_load.
>
> One of our purposes, notifying "I'm dying", would be achieved by purgatory
> code provided by kexec command as I stated before. Since the way of the
> notification will differ from each vendor, I think we need to modify
> the purgatory codes pluggable. Also, I think we need some parameter
> passing mechanism to the purgatory code. For example, passing the panic
> message via boot parameter to save it to SEL. Although I'm not sure
> we can do that (I've not investigated well yet). Is that acceptable?
I think the address of panic message is available in crash notes. If
not that is very reasonable to add.
Updating the SEL from purgatory after purgatory has validated the
checksums of the crash handling code is acceptable.
All that is desired is to run as little code as possible in a kernel
that is known broken. Once the checksums have verified things in
purgatory you should be in good shape, and there is no possibility of
relying on broken infrastructure because that code simply is not present
in purgatory.
We already have a few early_printk style drivers in purgatory and I
don't the code to update the SEL would be much worse.
On the flip side there are enough firmware bugs that I personally would
not want to rely on firmware code running properly when the machine is
in a known broken state, so I don't want the SEL update to be
unconditional.
Eric
next prev parent reply other threads:[~2015-08-05 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 1:16 [RFC V2 PATCH 0/1] kexec: crash_kexec_post_notifiers boot option related fixes Hidehiro Kawai
2015-07-24 1:16 ` [RFC V2 PATCH 1/1] panic/x86: Replace smp_send_stop() with crash_kexec version Hidehiro Kawai
2015-08-03 11:06 ` [RFC V2 PATCH 0/1] kexec: crash_kexec_post_notifiers boot option related fixes Hidehiro Kawai
2015-08-03 16:33 ` Eric W. Biederman
2015-08-04 11:41 ` 河合英宏 / KAWAI,HIDEHIRO
2015-08-05 17:10 ` Eric W. Biederman [this message]
2015-08-07 1:38 ` 河合英宏 / KAWAI,HIDEHIRO
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=87io8tvez5.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=dwalker@fifo99.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=vgoyal@redhat.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