Re: [PATCH] 2.5.19 daemonize calls reparent_init for you

From: Ingo Oeser (ingo.oeser@informatik.tu-chemnitz.de)
Date: Thu May 30 2002 - 05:05:05 EST

Next message: me@vger.org: "Re: Strange RAID2 behavier..."
Previous message: Peter Wächtler: "[PATCH] 2.4.19-pre8 fs/nfs/nfsroot.c - in_ntoa"
In reply to: Rusty Russell: "[PATCH] 2.5.19 daemonize calls reparent_init for you"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, May 30, 2002 at 03:05:07PM +1000, Rusty Russell wrote:
> daemonize() should call reparent_to_init: a classic mistake (I made it
> recently).
>
> Future potential cleanups:
> daemonize() should take mask of signals to allow
> kernel_thread() should take a name to copy into ->comm.

Why no generating kernel threads by basically cloning "init"?

This is what we do anyway (creating a clone of init with special
properties) but by cloning the current process and adjusting
everything needed later to make it appear of a mixture of init
clone and idle process clone.

Comments?

Regards

Ingo Oeser

-- 
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: me@vger.org: "Re: Strange RAID2 behavier..."
Previous message: Peter Wächtler: "[PATCH] 2.4.19-pre8 fs/nfs/nfsroot.c - in_ntoa"
In reply to: Rusty Russell: "[PATCH] 2.5.19 daemonize calls reparent_init for you"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri May 31 2002 - 22:00:28 EST