From: ebiederm@xmission.com (Eric W. Biederman)
To: vgoyal@in.ibm.com
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, 02 Jun 2006 10:39:42 -0600 [thread overview]
Message-ID: <m1irnj4ilt.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060602153717.GC29610@in.ibm.com> (Vivek Goyal's message of "Fri, 2 Jun 2006 11:37:17 -0400")
Vivek Goyal <vgoyal@in.ibm.com> writes:
> 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.
Yes.
Except when under tight time constraints this is clearly possible.
When under time constraints things are more dicy. I expect that
with a tuned kernel you can be back in user space in about 1 second.
Detecting a failure is hard and slow. Unless the condition that
triggers the panic is the initial source of the panic it is quite
likely a time window less than 1 second has already elapsed.
So I am certainly willing to discuss this but until I see a clear
model where a new kernel will not meet the time constraints for
some fairly fundamental reasons, and that a crash notifier
will almost always meet those same time constraints, I can't imagine
a persuasive case.
The panic notifier itself is barely used and it seems to exist
only because we didn't have a general purpose policy mechanism.
Eric
next prev parent reply other threads:[~2006-06-02 16:41 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 [this message]
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=m1irnj4ilt.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome