From: "Akiyama, Nobuyuki" <akiyama.nobuyuk@jp.fujitsu.com>
To: Preben Traerup <Preben.Trarup@ericsson.com>
Cc: ebiederm@xmission.com, fastboot@lists.osdl.org,
linux-kernel@vger.kernel.org, vgoyal@in.ibm.com
Subject: Re: [Fastboot] [RFC][PATCH] Add missing notifier before crashing
Date: Tue, 6 Jun 2006 20:08:37 +0900 [thread overview]
Message-ID: <20060606200837.3ad723c0.akiyama.nobuyuk@jp.fujitsu.com> (raw)
In-Reply-To: <44854C8D.6040707@ericsson.com>
On Tue, 06 Jun 2006 11:36:13 +0200
Preben Traerup <Preben.Trarup@ericsson.com> wrote:
> Eric W. Biederman wrote:
>
> >Preben Traerup <Preben.Trarup@ericsson.com> writes:
> >
> >
> >
> >
> >
> >>Since I'm apperantly not the only one left with this choice I rather prefer a
> >>solution
> >>made in public, that is known to be "bad" in some (well known) situations than
> >>each and everybody implements their own solution to the same problem.
> >>
> >>
> >
> >It is certainly worth discussing.
> >
> >Eric
> >
> >
> >
> To handle the contradiction of adding crash notifier to kexec and
> maintaining kexec reliability
> I suggest adding a flag to Kconfig
> ENABLE_CRASH_NOTIFIER
>
> This removes any code in the critical path for people not needing crash
> notification.
I am just thinking same thing, but one point is different.
To select policy by Kconfig is not flexible. If we want to change policy,
we have to rebuild the kernel. I don't think that distributors release
the kernels for each policy.
Instead of Kconfig, how about using proc filesystem. e.g. kdump_safe.
If kdump_safe is 1, crash notifier will not be called.
If kdump_safe is 0, crash notifier will be called.
Regards,
Akiyama, Nobuyuki
next prev parent reply other threads:[~2006-06-06 11:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 9:33 Akiyama, Nobuyuki
2006-05-30 14:56 ` [Fastboot] " Vivek Goyal
2006-05-31 9:20 ` Akiyama, Nobuyuki
2006-05-31 15:43 ` Vivek Goyal
2006-06-01 10:50 ` Preben Traerup
2006-06-01 12:37 ` Akiyama, Nobuyuki
2006-06-01 15:16 ` Vivek Goyal
2006-06-02 5:13 ` Akiyama, Nobuyuki
2006-06-02 10:08 ` Preben Traerup
2006-06-02 11:52 ` Eric W. Biederman
2006-06-02 13:20 ` Preben Traerup
2006-06-02 15:20 ` Eric W. Biederman
2006-06-02 15:37 ` Vivek Goyal
2006-06-02 16:39 ` Eric W. Biederman
2006-06-06 9:36 ` Preben Traerup
2006-06-06 11:08 ` Akiyama, Nobuyuki [this message]
2006-06-06 13:59 ` Akiyama, Nobuyuki
2006-06-02 14:53 ` Vivek Goyal
2006-06-05 11:46 ` Akiyama, Nobuyuki
2006-06-02 14:56 ` Vivek Goyal
2006-06-06 10:12 ` Preben Traerup
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=20060606200837.3ad723c0.akiyama.nobuyuk@jp.fujitsu.com \
--to=akiyama.nobuyuk@jp.fujitsu.com \
--cc=Preben.Trarup@ericsson.com \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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
all inboxes | Powered by JetHome®