public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Preben Traerup <Preben.Trarup@ericsson.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Akiyama, Nobuyuki" <akiyama.nobuyuk@jp.fujitsu.com>,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org,
	Vivek Goyal <vgoyal@in.ibm.com>
Subject: Re: [Fastboot] [RFC][PATCH] Add missing notifier before crashing
Date: Fri, 02 Jun 2006 15:20:31 +0200	[thread overview]
Message-ID: <44803B1F.8070302@ericsson.com> (raw)
In-Reply-To: <m1fyin6agv.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:

>
>You can put anything you want for crash_kexec to execute.
>
>If the problem is strictly limited to hardware failure and software
>can cope with that then don't panic the kernel and execute an orderly
>transition.
>
>If software cannot cope, and must panic the kernel it clearly cannot
>do something sensible.
>
>Eric
>
>  
>

Something like out of memory and oops-es are enough to deeme the system 
must panic
because it is simply not supposed to happen in a Telco server at any time.

kdump helps debugging these cases, but more importantly another server
must take over the work, and this has and always will have highest priority.

I'm happy about what crash_kexec does today, but the timing issue makes 
it unusable for
notifications to external systems, if I need to wait until properly 
running in next kernel.

That leaves me the choice of doing notification before executing 
crash_kexec ?
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.

./Preben

  reply	other threads:[~2006-06-02 13:20 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
2006-06-02 11:52               ` Eric W. Biederman
2006-06-02 13:20                 ` Preben Traerup [this message]
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=44803B1F.8070302@ericsson.com \
    --to=preben.trarup@ericsson.com \
    --cc=akiyama.nobuyuk@jp.fujitsu.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