From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Total system lockup with Alt-SysRQ-L
Date: Sun, 23 Dec 2001 17:58:46 +0000 [thread overview]
Message-ID: <20011223175846.B27993@flint.arm.linux.org.uk> (raw)
Ok, alt-sysrq-l is a pretty major thing to do, as it has the effect of
killing everything, including init.
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.
Back in 2.3, I had a go at fixing this, Linus rejected the patch saying
that it was doing the wrong thing. To this day, the kernel still suffers
from this, and I've not had the inclination to spend any more time on it.
So, I'm just letting people know that alt-sysrq-l is rather fatal,
especially if you want to do the following sequence to avoid a fsck:
alt-sysrq-l
alt-sysrq-s
alt-sysrq-u
alt-sysrq-b
IMHO either alt-sysrq-l should be removed, or someone who knows the logic
behind the linking of tasks together needs to fix exit_notify so it doesn't
enter an infinite loop when init exits.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next reply other threads:[~2001-12-23 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-23 17:58 Russell King [this message]
2001-12-24 2:34 ` Total system lockup with Alt-SysRQ-L Alan Cox
2001-12-24 8:37 ` Russell King
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=20011223175846.B27993@flint.arm.linux.org.uk \
--to=rmk@arm.linux.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