public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristis Makris <kristis.makris@asu.edu>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ham] Re: Gracefully killing kswapd, or any kernel thread
Date: Fri, 09 Sep 2005 15:20:15 -0700	[thread overview]
Message-ID: <1126304415.2727.27.camel@syd.mkgnu.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0509091513310.5663@chaos.analogic.com>

On Fri, 2005-09-09 at 15:20 -0400, linux-os (Dick Johnson) wrote:

> Because it's now defunct <Z>, a zombie, waiting for somebody to
> reap its return status. You are almost there, you need to issue
> the kernel equivalent of waitpid() (sys_waitpid) to grab that
> status and throw it away. That's what the code I showed you
> did when it would shut down and remove a module that had
> a kernel thread.

It turns out I had to port reparent_to_init() from 2.4 to 2.2 to get it
going. issuing a sys_wait4 wasn't enough. Apparently there was no way
for the built-in kernel threads to exit at all in the first place. I
hope 2.6 at least issues a reparent_to_init in kernel_thread().


      reply	other threads:[~2005-09-09 22:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 19:41 Gracefully killing kswapd, or any kernel thread Kristis Makris
2005-09-07 20:08 ` linux-os (Dick Johnson)
2005-09-07 21:07   ` [ham] " Kristis Makris
2005-09-07 22:31     ` Kyle Moffett
2005-09-07 22:36     ` linux-os (Dick Johnson)
2005-09-09 18:51       ` Kristis Makris
2005-09-09 19:20         ` linux-os (Dick Johnson)
2005-09-09 22:20           ` Kristis Makris [this message]

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=1126304415.2727.27.camel@syd.mkgnu.net \
    --to=kristis.makris@asu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /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