From: sukadev@us.ibm.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org, containers@lists.osdl.org,
Pavel Emelyanov <xemul@openvz.org>
Subject: Re: [RFC, PATCH] handle the multi-threaded init's exit() properly
Date: Mon, 6 Aug 2007 23:34:31 -0700 [thread overview]
Message-ID: <20070807063431.GB23036@us.ibm.com> (raw)
In-Reply-To: <20070806221824.22a78312.akpm@linux-foundation.org>
Andrew Morton [akpm@linux-foundation.org] wrote:
| On Tue, 7 Aug 2007 00:33:26 +0400 Oleg Nesterov <oleg@tv-sign.ru> wrote:
|
| > On 08/06, Andrew Morton wrote:
| > >
| > > On Fri, 3 Aug 2007 01:20:09 +0400 Oleg Nesterov <oleg@tv-sign.ru> wrote:
| > >
| > > > 2. We are playing games with ->nsproxy->pid_ns. This code is bogus today, and
| > > > it has to be changed anyway when we really support pid namespaces, just
| > > > remove it.
| > >
| > > This patch broke
| > >
| > > pid-namespaces-define-and-use-task_active_pid_ns-wrapper.patch. This hunk:
| > >
| > > ***************
| > > *** 908,915 ****
| > > if (unlikely(!tsk->pid))
| > > panic("Attempted to kill the idle task!");
| > > if (unlikely(tsk == child_reaper(tsk))) {
| > > - if (tsk->nsproxy->pid_ns != &init_pid_ns)
| > > - tsk->nsproxy->pid_ns->child_reaper = init_pid_ns.child_reaper;
| > > else
| > > panic("Attempted to kill init!");
| > > }
| > > --- 908,916 ----
| > > if (unlikely(!tsk->pid))
| > > panic("Attempted to kill the idle task!");
| > > if (unlikely(tsk == child_reaper(tsk))) {
| > > + if (task_active_pid_ns(tsk) != &init_pid_ns)
| > > + task_active_pid_ns(tsk)->child_reaper =
| > > + init_pid_ns.child_reaper;
| > > else
| > > panic("Attempted to kill init!");
| > > }
| > >
| > > has no place to live any more, so I just removed it.
| >
| > Ah, thanks. I should have done this patch against -mm tree.
| >
| > I hope it is OK to drop this chunk of
| > pid-namespaces-define-and-use-task_active_pid_ns-wrapper.patch
| >
| > Because it can't work right now anyway, and Sukadev+Pavel already have
| > new patches on top this one which make namespace switch actually work.
| >
|
| OK, well I had to make a bit of on-the-fly adjustment to
| pid-namespaces-rename-child_reaper-function.patch as well.
|
| The diff-of-the-diff is:
|
| @@ -48,7 +48,7 @@
| diff -puN kernel/exit.c~pid-namespaces-rename-child_reaper-function kernel/exit.c
| --- a/kernel/exit.c~pid-namespaces-rename-child_reaper-function
| +++ a/kernel/exit.c
| -@@ -694,7 +694,7 @@ forget_original_parent(struct task_struc
| +@@ -683,7 +683,7 @@ forget_original_parent(struct task_struc
| do {
| reaper = next_thread(reaper);
| if (reaper == father) {
| @@ -57,19 +57,10 @@
| break;
| }
| } while (reaper->exit_state);
| -@@ -907,7 +907,7 @@ fastcall NORET_TYPE void do_exit(long co
| - panic("Aiee, killing interrupt handler!");
| - if (unlikely(!tsk->pid))
| - panic("Attempted to kill the idle task!");
| -- if (unlikely(tsk == child_reaper(tsk))) {
| -+ if (unlikely(tsk == task_child_reaper(tsk))) {
| - if (task_active_pid_ns(tsk) != &init_pid_ns)
| - task_active_pid_ns(tsk)->child_reaper =
| - init_pid_ns.child_reaper;
| diff -puN kernel/signal.c~pid-namespaces-rename-child_reaper-function kernel/signal.c
|
| Hopefully people can re-review and retest what's there in next -mm.
|
| Or if that's too much work or too risky, option b) is to drop
| handle-the-multi-threaded-inits-exit-properly.patch, go back to the
| 2.6.23-rc1-mm2 versions of
| pid-namespaces-define-and-use-task_active_pid_ns-wrapper.patch and
| pid-namespaces-rename-child_reaper-function.patch and to ask Oleg to cook a 2.6.23-rc1-mm2 version of handle-the-multi-threaded-inits-exit-properly.patch.
|
| The downside of this approach is that
| handle-the-multi-threaded-inits-exit-properly.patch looks more 2.6.24-ready
| than all the container stuff (based just on overall impact and
| speculativeness)
Well, if it will help, we can drop these two patches from -mm, take Oleg's
patch and I can then resend these along with other pid ns patches.
pid-namespaces-define-and-use-task_active_pid_ns-wrapper.patch.
pid-namespaces-rename-child_reaper-function.patch
Suka
next prev parent reply other threads:[~2007-08-07 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 21:20 [RFC, PATCH] handle the multi-threaded init's exit() properly Oleg Nesterov
2007-08-02 22:51 ` Roland McGrath
2007-08-03 18:26 ` Oleg Nesterov
2007-08-06 20:13 ` Andrew Morton
2007-08-06 20:33 ` Oleg Nesterov
2007-08-07 5:18 ` Andrew Morton
2007-08-07 6:34 ` sukadev [this message]
2007-08-07 7:32 ` Andrew Morton
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=20070807063431.GB23036@us.ibm.com \
--to=sukadev@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
--cc=xemul@openvz.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