From: Andrew Morton <andrewm@uow.edu.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Rod Stewart <stewart@dystopia.lab43.org>,
linux-kernel@vger.kernel.org,
Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: 8139too: defunct threads
Date: Thu, 12 Apr 2001 13:18:07 -0700 [thread overview]
Message-ID: <3AD60D7F.1682DC7C@uow.edu.au> (raw)
In-Reply-To: <3AD5F9FE.9A49374D@uow.edu.au> from "Andrew Morton" at Apr 12, 2001 11:54:54 AM <E14nmpr-0001KH-00@the-village.bc.nu>
Alan Cox wrote:
>
> > <slaps head> swapper doesn't know how to reap children, and
> > AFAIK there's no way for a kernel thread to fully clean itself
> > up. This is always done by the parent.
>
> Make daemonize() move threads with parent 0 to parent 1
Reparenting would require diving inside this lot:
/*
* pointers to (original) parent process, youngest child, younger sibling,
* older sibling, respectively. (p->father can be replaced with
* p->p_pptr->pid)
*/
struct task_struct *p_opptr, *p_pptr, *p_cptr, *p_ysptr, *p_osptr;
struct list_head thread_group;
plus maybe rewriting pgrps, sessions, gids, etc. Challenging.
Plus it would mean that the kernel requires, for its
correct operation, that process "1" is a child reaper.
Is this a good thing?
next prev parent reply other threads:[~2001-04-12 20:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 17:58 8139too: defunct threads Rod Stewart
2001-04-12 18:54 ` Andrew Morton
2001-04-12 19:32 ` Alan Cox
2001-04-12 20:18 ` Andrew Morton [this message]
2001-04-12 21:15 ` Alan Cox
2001-04-12 19:37 ` Rod Stewart
2001-04-12 20:38 ` Andrew Morton
2001-04-12 21:23 ` Rod Stewart
2001-04-12 21:30 ` Andrew Morton
2001-04-12 21:33 ` Rod Stewart
2001-04-13 20:16 ` Rod Stewart
2001-04-12 22:19 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-04-14 14:00 Manfred Spraul
2001-04-14 16:21 ` Rod Stewart
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=3AD60D7F.1682DC7C@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stewart@dystopia.lab43.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