From: Andrew Morton <akpm@zip.com.au>
To: "Udo A. Steinberg" <reality@delusion.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.8-ac5
Date: Wed, 15 Aug 2001 11:09:49 -0700 [thread overview]
Message-ID: <3B7ABAEC.FA3797F8@zip.com.au> (raw)
In-Reply-To: <20010814221556.A7704@lightning.swansea.linux.org.uk> <3B79B43D.B9350226@delusion.de> <3B79C3A9.52562F71@zip.com.au> <3B79D26E.CD912961@delusion.de>
"Udo A. Steinberg" wrote:
>
> Andrew Morton wrote:
> >
> > Interesting that kpnpbiosd has a ppid of zero, whereas keventd, which
> > is started a few statements later has a ppid of one. hmmm..
>
> [...]
>
> > I bet this ancient reparent-kernel-thread-to-init patch fixes it. It always
> > does.
>
> It does indeed. Nice work, Andrew - works like a charm. Formerly the kpnpbios
> thread never exited, which is why the problem never showed, now it exits ok.
> I've rediffed your patch against 2.4.8-ac5, because I was getting rejects -
> in case Alan wants to apply it to his tree.
>
I think it's not ready. One possible problem is if a process
starts a kernel thread, then that thread calls daemonize() and
then someone waits on the thread's exit. With this patch they'll
hang, because the thread switched parents. I don't know if that
happens at present, but I suspect a better API is to make
reparent_to_init() a standalone API function, and call that from
places where it's appropriate.
Also, it should do other things like set the thread's UID, scheduling
parameters, etc to something sane (just copy them in from init_task).
So sigh. I guess I need to finish this off. But right now
I'm having too much fun writing
prepopulate-the-pagecache-with-stuff-to-make-it-boot-faster.c :)
-
next prev parent reply other threads:[~2001-08-15 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 21:15 Linux 2.4.8-ac5 Alan Cox
2001-08-14 23:29 ` Udo A. Steinberg
2001-08-15 0:34 ` Andrew Morton
2001-08-15 1:37 ` Udo A. Steinberg
2001-08-15 18:09 ` Andrew Morton [this message]
2001-08-15 1:36 ` Nathan Walp
2001-08-15 15:00 ` Eli Carter
2001-08-15 7:13 ` Paul
2001-08-15 8:37 ` Rik van Riel
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=3B7ABAEC.FA3797F8@zip.com.au \
--to=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=reality@delusion.de \
/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