public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Total system lockup with Alt-SysRQ-L
Date: Mon, 24 Dec 2001 08:37:52 +0000	[thread overview]
Message-ID: <20011224083752.A1181@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20011223175846.B27993@flint.arm.linux.org.uk> <E16IKwX-0002U3-00@the-village.bc.nu>
In-Reply-To: <E16IKwX-0002U3-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Dec 24, 2001 at 02:34:20AM +0000

On Mon, Dec 24, 2001 at 02:34:20AM +0000, Alan Cox wrote:
> > When pid1 exits (maybe due to a kill signal), we lockup hard in (iirc)
> > exit_notify.  I don't remember the details I'm afraid.
> 
> pid1 ends up trying to kill pid1 and it goes deeply down the toilet from
> that point onwards. The Unix traditional world reboots when pid 1 dies.

The problem was definitely in the exit_notify code, where it manipulated
the task links indefinitely.  (I think it was cptr never becomes null,
so the loop never terminates).

However, if we're saying that "pid1 must not die" then maybe we should get
rid of the 'killall' sysrq option since it serves no useful purpose, and
add a suitable panic in the do_exit path?

I'll generate a patch for that if there's interest.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-12-24  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-23 17:58 Total system lockup with Alt-SysRQ-L Russell King
2001-12-24  2:34 ` Alan Cox
2001-12-24  8:37   ` Russell King [this message]
2001-12-24 11:48     ` Denis Oliver Kropp
2001-12-24 12:26     ` Russell King
2001-12-25 11:33       ` Pavel Machek
2001-12-24 14:27     ` M. Edward (Ed) Borasky
2001-12-24 17:07       ` Alan Cox
2001-12-25 11:35         ` Pavel Machek
2001-12-28  1:00     ` David Woodhouse

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=20011224083752.A1181@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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