From: Roland McGrath <roland@redhat.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-os (Dick Johnson)" <linux-os@analogic.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel threads
Date: Thu, 8 Mar 2007 16:31:00 -0800 (PST) [thread overview]
Message-ID: <20070309003100.9893B180063@magilla.sf.frob.com> (raw)
In-Reply-To: Oleg Nesterov's message of Thursday, 8 March 2007 19:38:44 +0300 <20070308163844.GA6638@tv-sign.ru>
Your change seems fine to me. I certainly concur that it seems insane
for init to be responsible for tasks created magically inside the
kernel. The history I've found says that the setting to SIGCHLD was
introduced as part of "v2.5.1.9 -> v2.5.1.10", without detailed
commentary in the log. This was probably before the auto-reaping
semantics worked as they do now. So like the man said, at the time,
it seemed the logical thing to do.
To be paranoid, I wouldn't make this change in any stable kernel series.
It changes behavior visible to userland (init) from how it has been
consistently for five years, so, who knows, something might notice.
The old behavior is pretty harmless, albeit changing it seems both
preferable and harmless.
Thanks,
Roland
next prev parent reply other threads:[~2007-03-09 0:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 16:38 Kernel threads Oleg Nesterov
2007-03-09 0:31 ` Roland McGrath [this message]
2007-03-09 20:52 ` Oleg Nesterov
2007-03-09 21:38 ` Roland McGrath
2007-03-09 23:46 ` Oleg Nesterov
-- strict thread matches above, loose matches on Subject: below --
2007-03-06 16:03 linux-os (Dick Johnson)
2007-03-08 9:00 ` Andrew Morton
2002-11-20 9:36 kernel threads Madhavi
2002-04-12 17:07 Vahid Fereydunkolahi
2002-04-12 17:45 ` Masoud Sharbiani
2001-12-13 7:05 blesson paul
[not found] <no.id>
2001-08-16 22:37 ` Alan Cox
2001-08-21 12:15 ` Christian Widmer
2001-08-16 22:23 Christian Widmer
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=20070309003100.9893B180063@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=oleg@tv-sign.ru \
/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;
as well as URLs for NNTP newsgroup(s).