public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin Frey" <frey@scs.ch>
To: "'Benjamin Herrenschmidt'" <benh@kernel.crashing.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: kernel_thread vs. zombie
Date: Thu, 22 Mar 2001 06:32:52 -0800	[thread overview]
Message-ID: <004c01c0b2dc$fa6ab3e0$90600410@SCHLEPPDOWN> (raw)
In-Reply-To: <20010322114927.14509@mailhost.mipsys.com>

Hi,

>How do I force a kernel thread to always be a child of init and never
>become a zombie ?
>
>I do call daemonize at the beginning of the thread (as it won't do
>anything with files, signals or whatever), but that doesn't 
>seem to be enough.
>
Have a look at:
http://www.scs.ch/~frey/linux/kernelthreads.html
I have an example there that starts and stops kernel threads
from init_module and never produced a zombie.
I use the same code also to start threads from ioctl and it
works for me. I tested it on UP and SMP, Intel and Alpha,
2.2.18 and 2.4.2.

Regards,

Martin

-- 
Supercomputing Systems AG       email: frey@scs.ch
Martin Frey                     web:   http://www.scs.ch/~frey/
at Compaq Computer Corporation  phone: +1 603 884 4266
ZKO2-3P09, 110 Spit Brook Road, Nashua, NH 03062


  reply	other threads:[~2001-03-22 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 11:49 kernel_thread vs. zombie Benjamin Herrenschmidt
2001-03-22 14:32 ` Martin Frey [this message]
2001-03-22 15:07   ` Benjamin Herrenschmidt
2001-03-22 17:21     ` Martin Frey
2001-03-22 18:47       ` Benjamin Herrenschmidt
2001-03-22 19:50         ` Martin Frey
2001-03-22 23:33           ` Benjamin Herrenschmidt
2001-03-23  0:04             ` Andrew Morton
2001-03-23  1:57               ` Martin Frey
2001-03-23  2:13                 ` Andrew Morton
2001-03-23  8:06                   ` Martin Frey

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='004c01c0b2dc$fa6ab3e0$90600410@SCHLEPPDOWN' \
    --to=frey@scs.ch \
    --cc=benh@kernel.crashing.org \
    --cc=frey@cxau.zko.dec.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