From: Ralf Baechle <ralf@oss.sgi.com>
To: Atsushi Nemoto <nemoto@toshiba-tops.co.jp>
Cc: linux-mips@oss.sgi.com
Subject: Re: setup_frame() failure
Date: Fri, 14 Sep 2001 22:14:55 +0200 [thread overview]
Message-ID: <20010914221455.A2272@dea.linux-mips.net> (raw)
In-Reply-To: <20010914.111632.41627160.nemoto@toshiba-tops.co.jp>; from nemoto@toshiba-tops.co.jp on Fri, Sep 14, 2001 at 11:16:32AM +0900
On Fri, Sep 14, 2001 at 11:16:32AM +0900, Atsushi Nemoto wrote:
> ralf> The actual fix should be skipping over the faulting instruction
> ralf> when returning from the signal handler.
>
> Since the signal handler may want to know the faulting instruction,
> the "skipping" should be done AFTER the returning from the handler.
> On the other hand, the handler may do the "skipping" by itself...
>
> The symptom I reported first ("the process can not be killd by
> SIGKILL") does not occur if the signal handler executed successfully
> because do_signal() will be called when returning from sys_sygreturn.
> The symptom occur if setup_frame() failed. So I still think there is
> a point to check a failure of setup_frame().
Certain I/O models use a large number of signals so we're trying hard to
keep signal latency down. The current code already can guarantee proper
termination in case of a stack fault, just not the shortest way.
Ralf
next prev parent reply other threads:[~2001-09-14 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 11:26 setup_frame() failure Atsushi Nemoto
2001-09-07 23:36 ` Ralf Baechle
2001-09-10 2:44 ` Atsushi Nemoto
2001-09-12 4:09 ` Atsushi Nemoto
2001-09-13 1:11 ` Ralf Baechle
2001-09-14 2:16 ` Atsushi Nemoto
2001-09-14 20:14 ` Ralf Baechle [this message]
2001-09-17 3:28 ` Atsushi Nemoto
2001-09-10 7:28 ` Carsten Langgaard
2001-09-10 9:19 ` Ralf Baechle
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=20010914221455.A2272@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=nemoto@toshiba-tops.co.jp \
/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.