From: Oleg Nesterov <oleg@redhat.com>
To: Kirill Tkhai <ktkhai@odin.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] exit: Clarify choice of new parent in forget_original_parent()
Date: Tue, 16 Jun 2015 21:27:59 +0200 [thread overview]
Message-ID: <20150616192759.GA28955@redhat.com> (raw)
In-Reply-To: <1434448194.1711.1.camel@odin.com>
On 06/16, Kirill Tkhai wrote:
>
> Second parameter of find_new_reaper() and the similarity of its name
> and find_child_reaper()'s name confuse a reader.
OK, I agree that
reaper = find_child_reaper(father);
...
reaper = find_new_reaper(father, reaper);
can look confusing and probably deserves a cleanup. How about the patch
below then?
> Rename find_child_reaper() for better conformity of its name and its
> function.
I never argueus with renames ;) Probably the new name looks better.
> Also delete the second parameter of find_new_reaper().
Yes, we can do this. But this 2nd argument avoids another another
task_active_pid_ns(father)->child_reaper, so this is optimization.
I agree, this optimization is minor, but still I think this change
needs some justification.
> +static struct task_struct *find_new_reaper(struct task_struct *father)
> {
> - struct task_struct *thread, *reaper;
> + struct task_struct *thread, *reaper, *child_reaper;
>
> thread = find_alive_thread(father);
> if (thread)
> return thread;
>
> + child_reaper = task_active_pid_ns(father)->child_reaper;
> + /*
> + * child_reaper doesn't have children after zap_pid_ns_processes(),
> + * therefore it can't enter this function.
> + */
> + BUG_ON(child_reaper == father);
Yes, we can add this BUG_ON(). But please see the comments in
zap_pid_ns_processes(). We can change zap_pid_ns_processes() so that
it returns with non-empty ->children list due to EXIT_DEAD children.
Unlikely we will actually do this, at least soon, so I won't argue
with this BUG_ON().
But. In this case it would be better to add it into forget_original_parent(),
reaper = find_new_reaper(...);
BUG_ON(reaper == father);
Oh. Off-topic, but this reminds me that I forgot about another bug with
->has_child_subreaper... this needs another discussion.
Oleg.
--- x/kernel/exit.c
+++ x/kernel/exit.c
@@ -551,17 +551,17 @@ static void reparent_leader(struct task_
static void forget_original_parent(struct task_struct *father,
struct list_head *dead)
{
- struct task_struct *p, *t, *reaper;
+ struct task_struct *p, *t, *child_reaper, *reaper;
if (unlikely(!list_empty(&father->ptraced)))
exit_ptrace(father, dead);
/* Can drop and reacquire tasklist_lock */
- reaper = find_child_reaper(father);
+ child_reaper = find_child_reaper(father);
if (list_empty(&father->children))
return;
- reaper = find_new_reaper(father, reaper);
+ reaper = find_new_reaper(father, child_reaper);
list_for_each_entry(p, &father->children, sibling) {
for_each_thread(p, t) {
t->real_parent = reaper;
next prev parent reply other threads:[~2015-06-16 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 9:49 [PATCH] exit: Clarify choice of new parent in forget_original_parent() Kirill Tkhai
2015-06-16 19:27 ` Oleg Nesterov [this message]
2015-06-16 20:03 ` Oleg Nesterov
2015-06-17 17:24 ` Kirill Tkhai
2015-06-17 17:23 ` Kirill Tkhai
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=20150616192759.GA28955@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ktkhai@odin.com \
--cc=linux-kernel@vger.kernel.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