From: Ralf Baechle <ralf@linux-mips.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: Unknown traps.
Date: Wed, 24 Nov 2004 19:29:49 +0100 [thread overview]
Message-ID: <20041124182949.GF21039@linux-mips.org> (raw)
In-Reply-To: <OF7180588E.55ED6DF4-ON41256F56.00528D36-41256F56.005316AF@de.ibm.com>
On Wed, Nov 24, 2004 at 04:07:32PM +0100, Martin Schwidefsky wrote:
> Makes sense, although to panic if the fault happened in user space
> is a bit too harsh, isn't it? A do_exit(SIGSEGV) if the fault took place
> in user space and a panic if it happened in the kernel is my favorite
> at the moment.
There are asynchrous exceptions that can be delivered with significant
delay. So could have been caused by kernel, peripherals or even a
previous processor. Since for an unknown exception we by definition
don't know the cause or or state of the system after the exception or
how to clear the condition that is causing the exception I still think
panic is the right thing to do.
> blue skies,
Grey skies ...
Ralf
prev parent reply other threads:[~2004-11-24 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 13:27 Unknown traps Martin Schwidefsky
2004-11-22 14:29 ` Ralf Baechle
2004-11-24 15:07 ` Martin Schwidefsky
2004-11-24 18:29 ` Ralf Baechle [this message]
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=20041124182949.GF21039@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-arch@vger.kernel.org \
--cc=schwidefsky@de.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