From: Vivek Goyal <vgoyal@in.ibm.com>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Preben Traerup <Preben.Trarup@ericsson.com>,
"Akiyama, Nobuyuki" <akiyama.nobuyuk@jp.fujitsu.com>,
fastboot@lists.osdl.org,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] [RFC][PATCH] Add missing notifier before crashing
Date: Fri, 2 Jun 2006 11:37:17 -0400 [thread overview]
Message-ID: <20060602153717.GC29610@in.ibm.com> (raw)
In-Reply-To: <m13ben60tn.fsf@ebiederm.dsl.xmission.com>
On Fri, Jun 02, 2006 at 09:20:52AM -0600, Eric W. Biederman wrote:
> Preben Traerup <Preben.Trarup@ericsson.com> writes:
>
> > 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.
>
> That is clearly enough to deem that the system must take some sever action and
> stop running. You don't necessarily have to handle it through a kernel panic.
>
> > 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.
>
> Nothing says you have to wait until properly running in the next kernel.
> You can also write a dedicated piece of code that just pushes one packet
> out the NIC. Then you can start up a kernel for analysis purposes.
>
So basically the idea is that whatever one wants to do it should be done
in the next kernel, even notifications. But this might require some data
from the context of previous kernel, for example destination IP address etc.
So the associated data either needs to be passed to new kernel or it shall
have to be retrieved from permanent storage or something like that.
Thanks
Vivek
next prev parent reply other threads:[~2006-06-02 15:37 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
2006-06-02 15:20 ` Eric W. Biederman
2006-06-02 15:37 ` Vivek Goyal [this message]
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=20060602153717.GC29610@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=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 \
/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