Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
Subject: Re: unkillable process due to setup_frame() failure
Date: Wed, 7 Sep 2005 14:47:17 +0100	[thread overview]
Message-ID: <20050907134717.GA3493@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.61L.0509071011560.4591@blysk.ds.pg.gda.pl>

On Wed, Sep 07, 2005 at 10:14:16AM +0100, Maciej W. Rozycki wrote:

> > > So, the process can not be kill by SIGKILL.  In 2.6.12, 'sigkill
> > > priority fix' was applied to __dequeue_signal(), but it does not help
> > > while the SIGTRAP is queued to tsk->pending but SIGKILL (by kill
> > > command) is queued to tsk->signal->shared_pending.
> > 
> > The behaviour of not advancing the EPC beyond the faulting instruction is
> > part of the problem - but I believe that was the usual behaviour for
> > MIPS UNIXoid operating systems.
> 
>  Well, SIGKILL should always work and frankly I can't see a reason to 
> return back to user space in the affected context in the first place.  
> What's left in EPC shouldn't matter.

I said it's part of the problem - not that it should be changed.  The
behaviour as far as I can say is also standard for MIPS unixoid operating
systems.  That said, I definately prefer the approach of Atushi's suggested
fix #2.  The other question is why we try to continue if delivering a
signal failed and we already know that repeated attempts would fail again.

  Ralf

  reply	other threads:[~2005-09-07 13:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 16:42 unkillable process due to setup_frame() failure Atsushi Nemoto
2005-09-06 18:41 ` Ralf Baechle
2005-09-07  9:14   ` Maciej W. Rozycki
2005-09-07 13:47     ` Ralf Baechle [this message]
2005-09-07 14:44       ` Atsushi Nemoto
2005-09-07 14:56         ` Atsushi Nemoto
2005-09-07 15:24         ` Maciej W. Rozycki
2005-09-07 16:11           ` Ralf Baechle
2005-09-07 16:34             ` Maciej W. Rozycki
2005-09-15 16:17         ` Atsushi Nemoto
2005-09-15 16:44           ` 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=20050907134717.GA3493@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    /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