From: OBATA Noboru <noboru.obata.ar@hitachi.com>
To: tytso@mit.edu, hugh@veritas.com
Cc: lkml@oxley.org, pavel@ucw.cz, hyoshiok@miraclelinux.com,
linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Dump Summit 2005
Date: Thu, 27 Oct 2005 16:48:04 +0900 (JST) [thread overview]
Message-ID: <20051027.164804.63130901.noboru.obata.ar@hitachi.com> (raw)
In-Reply-To: <20051019190013.GD10969@thunk.org>
On Wed, 19 Oct 2005, "Theodore Ts'o" wrote:
>
> On Tue, Oct 18, 2005 at 03:10:24PM +0100, Hugh Dickins wrote:
> > On Tue, 18 Oct 2005, OBATA Noboru wrote:
> > >
> > > I have a bitter experience in analyzing a partial dump. The
> > > dump completely lacks the PTE pages of user processes and I had
> > > to give up analysis then. A partial dump has a risk of failure
> > > in analysis.
> >
> > Page tables of user processes are very often essential in a dump.
> > Data pages of user processes are almost always just a waste of
> > space and time in a dump. Please don't judge against partial
> > dumps on the basis of one that was badly selected.
My apologies. What should be blamed was the bad partial dump
implementation and not the partial dump itself.
But I don't think data pages of user processes are almost always
useless, as Ted comments.
> We've had hard-to-reproduce problems out in the field where being able
> to find the data pages of the user process was critical to figuring
> out what the heck was going on. So I wouldn't be quite so eager to
> dismiss the need for user pages. There are times when they come in
> quite handy....
I agree.
When a system crashed, a user may want to _avoid_ the cause of
crash and continue operation, until bugs are fixed and well
tested.
Then we try to find the way to avoid the specific situation that
has caused the crash. Sometimes it can be done by changing
resource limits, timeouts, or some fancy features in XXX.conf of
user programs.
To investigate the behavior of user processes, having data pages
of user processes in a dump is mandatory.
Regards,
--
OBATA Noboru (noboru.obata.ar@hitachi.com)
next prev parent reply other threads:[~2005-10-27 7:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 11:55 Hiro Yoshioka
2005-10-06 12:17 ` OBATA Noboru
2005-10-06 14:39 ` Hiro Yoshioka
2005-10-10 8:45 ` Pavel Machek
2005-10-12 8:28 ` OBATA Noboru
2005-10-12 9:02 ` Felix Oxley
2005-10-12 9:09 ` Pavel Machek
2005-10-12 9:56 ` Felix Oxley
2005-10-12 10:07 ` Pavel Machek
2005-10-12 18:03 ` Andy Isaacson
2005-10-12 22:34 ` Felix Oxley
2005-10-12 11:05 ` jerome lacoste
2005-10-12 21:10 ` Felix Oxley
2005-10-18 13:47 ` OBATA Noboru
2005-10-18 14:10 ` Hugh Dickins
2005-10-19 19:00 ` Theodore Ts'o
2005-10-27 7:48 ` OBATA Noboru [this message]
2005-10-11 0:49 ` Andrew Morton
2005-10-11 4:41 ` Hiro Yoshioka
2005-10-12 8:30 ` OBATA Noboru
2005-10-13 5:49 ` Maneesh Soni
2005-10-27 7:45 ` OBATA Noboru
2005-10-13 14:28 ` Troy Heber
2005-10-17 11:19 ` Takao Indoh
2005-10-18 13:48 ` OBATA Noboru
2005-10-19 3:17 ` Takao Indoh
2005-10-27 7:45 ` OBATA Noboru
2005-10-18 14:54 ` Carsten Otte
2005-10-14 9:19 hideki.takahashi
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=20051027.164804.63130901.noboru.obata.ar@hitachi.com \
--to=noboru.obata.ar@hitachi.com \
--cc=hugh@veritas.com \
--cc=hyoshiok@miraclelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@oxley.org \
--cc=pavel@ucw.cz \
--cc=tytso@mit.edu \
/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®