From: Russell King <rmk@arm.linux.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4 and 2.5: remove Alt-Sysrq-L
Date: Fri, 15 Mar 2002 14:42:37 +0000 [thread overview]
Message-ID: <20020315144237.G24984@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020315142854.E24984@flint.arm.linux.org.uk> <20020315131612.C24984@flint.arm.linux.org.uk> <30439.1016201464@redhat.com> <20020315142854.E24984@flint.arm.linux.org.uk> <1901.1016202759@redhat.com>
In-Reply-To: <1901.1016202759@redhat.com>; from dwmw2@infradead.org on Fri, Mar 15, 2002 at 02:32:39PM +0000
On Fri, Mar 15, 2002 at 02:32:39PM +0000, David Woodhouse wrote:
> rmk@arm.linux.org.uk said:
> > Well, I've tried this approach, Linus rejected it.
> > If you'd like to take up this problem, be my guest.
>
> Not really - I also tried already. But I'm disinclined to offer band-aids
> for the brokenness.
I don't know of any Linux kernel that has ever been able to cope with PID1
dying. I certainly remember facing the PID1 dying causing lockup as far
back as 1.3 kernels, and I even tried to fix it back then. The argument
put forward for not fixing it is that PID1 should not exit. Period.
The point here is not that the kernel itself can't cope with PID1 exiting,
but that the code _bypasses_ the protection put into the kernel against
PID1 exiting.
--
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 14:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 13:16 [PATCH] 2.4 and 2.5: remove Alt-Sysrq-L 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 [this message]
2002-03-15 14:46 ` David Woodhouse
2002-03-15 14:54 Nicholas Berry
2002-03-15 15:02 ` Russell King
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
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=20020315144237.G24984@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dwmw2@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).