From: ebiederm@xmission.com (Eric W. Biederman)
To: "Akiyama, Nobuyuki" <akiyama.nobuyuk@jp.fujitsu.com>
Cc: fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] [PATCH] kdump: add a missing notifier before crashing
Date: Wed, 05 Jul 2006 10:14:20 -0600 [thread overview]
Message-ID: <m1fyhg3u77.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060704213301.4701055e.akiyama.nobuyuk@jp.fujitsu.com> (Nobuyuki Akiyama's message of "Tue, 4 Jul 2006 21:33:01 +0900")
"Akiyama, Nobuyuki" <akiyama.nobuyuk@jp.fujitsu.com> writes:
> Hi all,
>
> The attached patch adds a missing notifier before crashing.
NAK
It's not missing. It should not exist.
> This patch is remade for 2.6.17-git22.
> I tested this patch on a i386-box.
>
> Please refer to the previous discussions for details:
> http://lists.osdl.org/pipermail/fastboot/2006-May/003018.html
> http://lists.osdl.org/pipermail/fastboot/2006-June/003113.html
>
> Description:
> We don't have a simple and light weight way to know the
> kernel dies. The panic notifier does not be called if kdump
> is activated because crash_kexec() does not return,
> and there is no mechanism to notify of a crash before
> crashing by SysRq-c.
> Although notify_die() exists, but the function depends on
> architecture. If notify_die() is added in panic and SysRq
> respectively like existing implementation, the code will be
> very ugly. I think that adding a generic hook in crash_kexec()
> is better to simplify the code.
>
> For example, the clustering system can take advantage of this
> notifier. On a mission critical system, failover needs to start
> within a few milli-second. The notifier could be called on
> 2nd kernel, but it is no use because it takes the time of
> second order to boot up.
>
> On an actual system, the notifier turns off HBA's power to
> stop accessing shared disk, and then notifies standby node
> that the current node died.
And again NAK.
Just call the stupid HBA routine directly if this is necessary.
The call can compile to nothing when you HBA is not compiled in.
This is completely unacceptable until we see the code that you are
calling.
If we do export your notifier list it needs to be at least a
GPL only export as this is very much in the guts of the kernel.
As written this seriously destabilizes the kexec on panic support.
I will happy to have a solution to this problem but not this solution.
Especially not without an in-kernel user.
Nacked-by: Eric Biederman <ebiederm@xmission.com>
Eric
next prev parent reply other threads:[~2006-07-05 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 12:33 Akiyama, Nobuyuki
2006-07-05 16:14 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-15 11:16 Akiyama, Nobuyuki
2006-06-16 6:28 ` [Fastboot] " Eric W. Biederman
2006-06-16 12:15 ` Akiyama, Nobuyuki
2006-06-16 16:37 ` Eric W. Biederman
2006-06-19 7:30 ` Akiyama, Nobuyuki
2006-06-19 12:47 ` Eric W. Biederman
2006-06-19 13:28 ` Preben Traerup
2006-06-19 16:49 ` Eric W. Biederman
2006-06-19 17:07 ` Vivek Goyal
2006-06-19 17:50 ` Eric W. Biederman
2006-06-19 18:19 ` Vivek Goyal
2006-06-19 18:45 ` Eric W. Biederman
2006-06-20 3:46 ` Akiyama, Nobuyuki
2006-06-20 3:39 ` Akiyama, Nobuyuki
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=m1fyhg3u77.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akiyama.nobuyuk@jp.fujitsu.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®