mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin Frey" <frey@scs.ch>
To: "'Andrew Morton'" <andrewm@uow.edu.au>,
	"'Benjamin Herrenschmidt'" <benh@kernel.crashing.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: kernel_thread vs. zombie
Date: Thu, 22 Mar 2001 17:57:51 -0800	[thread overview]
Message-ID: <008901c0b33c$ab1f51a0$90600410@SCHLEPPDOWN> (raw)
In-Reply-To: <3ABA92F0.CF6729C2@uow.edu.au>

>>  - When started during boot (low PID (9)) It becomes a zombie
>>  - When started from a process that quits after sending the ioctl,
>>    it is correctly "garbage collected".
>>  - When started from a process that stays around, it becomes 
>>    a zombie too

>Take a look at kernel/kmod.c:call_usermodehelper().  Copy it.
>
>This will make your thread a child of keventd.  This takes
>care of things like chrootedness, uids, cwds, signal masks,
>reaping children, open files, and all the other crud which
>you can accidentally inherit from your caller.
>
So depending on the state of the caller daemonize() will not really
put us into the background as we want. With being created from
keventd we inherit a state as we'd like to have in a kernel thread.
Did I get it right?
I will change my example and test that.

Thanks,

Martin

  reply	other threads:[~2001-03-23  1:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 11:49 Benjamin Herrenschmidt
2001-03-22 14:32 ` Martin Frey
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 [this message]
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='008901c0b33c$ab1f51a0$90600410@SCHLEPPDOWN' \
    --to=frey@scs.ch \
    --cc=andrewm@uow.edu.au \
    --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
all inboxes | Powered by JetHome®