All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: 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, 09 Oct 2001 09:13:50 -0700	[thread overview]
Message-ID: <3BC3223E.902FB7E@zip.com.au> (raw)
In-Reply-To: <3BC3118B.8050001@wipro.com>

BALBIR SINGH wrote:
> 
> I was looking at the driver under drivers/net/8139too.c, a kernel
> thread rtl8139_thread is created, it calls daemonize() and soon
> afterwards calls reparent_to_init(). Looking at reparent_to_init(),
> it looks like all kernel threads should do this. But, I feel I am missing
> something, since not everybody does this.
> 
> Is this a good thing to do? or are there special cases when we need this.
> 

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.

  reply	other threads:[~2001-10-09 16:14 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 [this message]
2001-10-09 20:26   ` Rob Landley
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=3BC3223E.902FB7E@zip.com.au \
    --to=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 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.