From: Andrei Vagin <avagin@gmail.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>
Cc: linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] kernel: release ptraced tasks before zap_pid_ns_processes
Date: Wed, 2 Jan 2019 13:17:21 -0800 [thread overview]
Message-ID: <20190102211720.GB3237@gmail.com> (raw)
In-Reply-To: <20190102205939.26231-1-avagin@gmail.com>
Oops, Al is here by mistake. Sorry about that.
On Wed, Jan 02, 2019 at 12:59:39PM -0800, Andrei Vagin wrote:
> Currently, exit_ptrace() adds all ptraced tasks in a dead list, than
> zap_pid_ns_processes() waits all tasks in a current pid ns, and only
> then tasks from the dead list are released.
>
> zap_pid_ns_processes() can stuck on waiting tasks from the dead list. In
> this case, we will have one unkillable process with one or more dead
> children.
>
> Cc: Oleg Nesterov <oleg@redhat.com>
> Cc: "Eric W. Biederman" <ebiederm@xmission.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Andrei Vagin <avagin@gmail.com>
> ---
> kernel/exit.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/exit.c b/kernel/exit.c
> index 0e21e6d21f35..ccaa6f6549ba 100644
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -664,9 +664,6 @@ static void forget_original_parent(struct task_struct *father,
> {
> struct task_struct *p, *t, *reaper;
>
> - if (unlikely(!list_empty(&father->ptraced)))
> - exit_ptrace(father, dead);
> -
> /* Can drop and reacquire tasklist_lock */
> reaper = find_child_reaper(father);
> if (list_empty(&father->children))
> @@ -705,8 +702,18 @@ static void exit_notify(struct task_struct *tsk, int group_dead)
> LIST_HEAD(dead);
>
> write_lock_irq(&tasklist_lock);
> - forget_original_parent(tsk, &dead);
> + if (unlikely(!list_empty(&tsk->ptraced)))
> + exit_ptrace(tsk, &dead);
> + write_unlock_irq(&tasklist_lock);
> +
> + /* Ptraced tasks have to be released before zap_pid_ns_processes(). */
> + list_for_each_entry_safe(p, n, &dead, ptrace_entry) {
> + list_del_init(&p->ptrace_entry);
> + release_task(p);
> + }
>
> + write_lock_irq(&tasklist_lock);
> + forget_original_parent(tsk, &dead);
> if (group_dead)
> kill_orphaned_pgrp(tsk->group_leader, NULL);
>
> --
> 2.17.2
>
next prev parent reply other threads:[~2019-01-02 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 20:59 [PATCH] kernel: release ptraced tasks before zap_pid_ns_processes Andrei Vagin
2019-01-02 21:16 ` Andrei Vagin
2019-01-02 21:17 ` Andrei Vagin [this message]
2019-01-08 16:50 ` Oleg Nesterov
2019-01-08 20:36 ` Andrei Vagin
2019-01-09 17:08 ` Oleg Nesterov
2019-01-10 8:36 ` Andrei Vagin
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=20190102211720.GB3237@gmail.com \
--to=avagin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.