From: Kuba Ober <kuba@mareimbrium.org>
To: "K.Morikawa" <k-morikawa@stage.gr.jp>
Cc: reiserfs-list@namesys.com
Subject: Re: kernel panic with PAP-8252
Date: Tue, 30 Jul 2002 09:08:55 -0400 [thread overview]
Message-ID: <200207300908.55739.kuba@mareimbrium.org> (raw)
In-Reply-To: <20020730211933.2D2F.K-MORIKAWA@stage.gr.jp>
On wtorek 30 lipiec 2002 08:20 am, K.Morikawa wrote:
> Hello.
> Thank you for your reply.
>
> I understand that kernel-2.2.18 and reiserfs-3.5.29 is old.
> Also reiserfs-3.5.35(latest) is fixed many bugs too.
> However, it is unable to up the version immediately.
> because cause of this problem is indistinct and
> It's necessary the inspection of the middleware and application related.
By definition, user-level, unprivileged application errors shouldn't crash the
kernel. So you should really forget about your application stuff and update
the kernel to the latest 2.2, as well as latest reiserfs for 2.2. Or else
you're asking for trouble.
Again: application stuff should not crash the kernel if the kernel is fine. So
even if your apps were completely broken, the kernel should be running fine.
If you're getting kernel crashes, it's the kernel at fault. *Do* update ASAP.
*Really*. You know, updating the kernel is not such a big job after all.
Cheers, Kuba Ober
next prev parent reply other threads:[~2002-07-30 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 6:11 kernel panic with PAP-8252 K.Morikawa
2002-07-30 11:03 ` Oleg Drokin
2002-07-30 12:20 ` K.Morikawa
2002-07-30 12:26 ` Oleg Drokin
2002-07-30 12:52 ` K.Morikawa
2002-07-30 13:02 ` Oleg Drokin
2002-07-30 13:08 ` Kuba Ober [this message]
2002-07-30 13:13 ` Kuba Ober
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=200207300908.55739.kuba@mareimbrium.org \
--to=kuba@mareimbrium.org \
--cc=k-morikawa@stage.gr.jp \
--cc=reiserfs-list@namesys.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.