From: Preben Traerup <Preben.Trarup@ericsson.com>
To: "Akiyama, Nobuyuki" <akiyama.nobuyuk@jp.fujitsu.com>
Cc: vgoyal@in.ibm.com, fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] [RFC][PATCH] Add missing notifier before crashing
Date: Fri, 02 Jun 2006 12:08:26 +0200 [thread overview]
Message-ID: <44800E1A.1080306@ericsson.com> (raw)
In-Reply-To: <20060602141301.cdecf0e1.akiyama.nobuyuk@jp.fujitsu.com>
Akiyama, Nobuyuki wrote:
>
>I don't think all people will use kdump(but I recommend my customer
>to use kdump ;-).
>The aim of panic notifier and crash notifier is a little different,
>so I thought these notifier lists should be separated.
>The panic notifier was not expected of kdump after notifier return!
>I think the better way is to modify panic notifiers to fit with
>kdump and to move into crash notifier gradually if necessary.
>
>
>
Since I'm one of the people who very much would like best of both worlds,
I do belive Vivek Goyal's concern about the reliability of kdump must be
adressed properly.
I do belive the crash notifier should at least be a list of its own.
Attaching element to the list proves your are kdump aware - in theory
However:
Conceptually I do not like the princip of implementing crash notifier
as a list simply because for all (our) practical usage there will only
be one element attached to the list anyway.
And as I belive crash notifiers only will be used by a very limited
number of users, I suggested in another mail that a simple
if (function pointer)
call functon
approach to be used for this special case to keep things very simple.
./Preben
next prev parent reply other threads:[~2006-06-02 10:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 9:33 [RFC][PATCH] Add missing notifier before crashing 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 [this message]
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
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=44800E1A.1080306@ericsson.com \
--to=preben.trarup@ericsson.com \
--cc=akiyama.nobuyuk@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.