From: Rob Landley <landley@trommello.org>
To: Andrew Morton <akpm@zip.com.au>, BALBIR SINGH <balbir.singh@wipro.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: is reparent_to_init a good thing to do?
Date: Tue, 9 Oct 2001 16:26:18 -0400 [thread overview]
Message-ID: <01100916261802.09423@localhost.localdomain> (raw)
In-Reply-To: <3BC3118B.8050001@wipro.com> <3BC3223E.902FB7E@zip.com.au>
In-Reply-To: <3BC3223E.902FB7E@zip.com.au>
On Tuesday 09 October 2001 12:13, Andrew Morton wrote:
> I think yes, more kernel threads need to use this function. Most
> particularly, threads which are parented by a userspace application
> and which can terminate. For example, the nfsd threads.
>
> Right now, it's probably the case that nfsd threads will turn
> into zombies when they terminate, *if* their parent is still
> running. But of course, most kernel threads are parented
> by very short-lived userspace applications, so nobody has
> ever noticed.
Or long lived kernel threads from short lived login sessions.
You have a headless gateway box for your local subnet, administered via ssh
from a machine on the local subnet. So you SSH into the box through eth1,
ifconfig eth0 down back up again. If eth0 is an rtl8039too, this fires off a
kernel thread (which, before reparent_to_init, was parented to your ssh login
session).
Now exit the login session. SSH does not exit until all the child processes
exit, so it just hangs there until you kill it from another console window...
Rob
next prev parent reply other threads:[~2001-10-10 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 15:02 is reparent_to_init a good thing to do? BALBIR SINGH
2001-10-09 16:13 ` Andrew Morton
2001-10-09 20:26 ` Rob Landley [this message]
2001-10-10 11:17 ` BALBIR SINGH
2001-10-10 13:02 ` BALBIR SINGH
2001-10-10 22:13 ` Rob Landley
[not found] ` <mailman.1002644159.30689.linux-kernel2news@redhat.com>
2001-10-09 18:46 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 14:38 Jesse Pollard
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=01100916261802.09423@localhost.localdomain \
--to=landley@trommello.org \
--cc=akpm@zip.com.au \
--cc=balbir.singh@wipro.com \
--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