From: Russell King <rmk@arm.linux.org.uk>
To: Kasper Dupont <kasperd@daimi.au.dk>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4 and 2.5: remove Alt-Sysrq-L
Date: Tue, 19 Mar 2002 16:28:40 +0000 [thread overview]
Message-ID: <20020319162840.F11739@flint.arm.linux.org.uk> (raw)
In-Reply-To: <sc91c4ce.020@mail-01.med.umich.edu> <20020315150241.H24984@flint.arm.linux.org.uk> <3C96F015.24BDC9FF@daimi.au.dk>
On Tue, Mar 19, 2002 at 09:00:21AM +0100, Kasper Dupont wrote:
> Russell King wrote:
> >
> > With all recent kernels, init exiting causes the last of these to trigger:
> >
> > NORET_TYPE void do_exit(long code)
> > {
> > struct task_struct *tsk = current;
> >
> > if (in_interrupt())
> > panic("Aiee, killing interrupt handler!");
> > if (!tsk->pid)
> > panic("Attempted to kill the idle task!");
> > if (tsk->pid == 1)
> > panic("Attempted to kill init!");
>
> Why actually panic because of an attempt to kill init?
>
> Of course a message should be printed, but after that
> couldn't do_exit enter a loop where it just handles
> signals and zombies?
Examine the LKML archive around 23rd December 2001, where Alan Cox wrote:
| 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.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-03-19 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 14:54 [PATCH] 2.4 and 2.5: remove Alt-Sysrq-L Nicholas Berry
2002-03-15 15:02 ` Russell King
2002-03-19 8:00 ` Kasper Dupont
2002-03-19 16:28 ` Russell King [this message]
2002-03-19 21:30 ` Kasper Dupont
2002-03-20 0:22 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-03-15 13:16 Russell King
2002-03-15 14:11 ` David Woodhouse
2002-03-15 14:28 ` Russell King
2002-03-15 14:32 ` David Woodhouse
2002-03-15 14:42 ` Russell King
2002-03-15 14:46 ` 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=20020319162840.F11739@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=kasperd@daimi.au.dk \
--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 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.