From: Russell King <rmk@arm.linux.org.uk>
To: Nicholas Berry <nikberry@med.umich.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4 and 2.5: remove Alt-Sysrq-L
Date: Fri, 15 Mar 2002 15:02:41 +0000 [thread overview]
Message-ID: <20020315150241.H24984@flint.arm.linux.org.uk> (raw)
In-Reply-To: <sc91c4ce.020@mail-01.med.umich.edu>
In-Reply-To: <sc91c4ce.020@mail-01.med.umich.edu>; from nikberry@med.umich.edu on Fri, Mar 15, 2002 at 09:54:05AM -0500
On Fri, Mar 15, 2002 at 09:54:05AM -0500, Nicholas Berry wrote:
> > I distinctly recall it working perfectly OK in around 2.1.50. I had boxen
> > where /sbin/init was a shell script which would bring up the interfaces,
> > enable routing, and exit.
>
> That's a different thing, I think.
>
> That is, 'init exiting' versus 'all the code to prevent init being killed
> is bypassed and init is killed'
Very true.
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!");
It is this very test that Alt-SysRQ-L is attempting to bypass which causes
the problem.
--
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-15 15:03 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 [this message]
2002-03-19 8:00 ` Kasper Dupont
2002-03-19 16:28 ` Russell King
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=20020315150241.H24984@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nikberry@med.umich.edu \
/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.