From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleg Nesterov Subject: Re: [PATCH 4/9] pid: Generalize task_active_pid_ns Date: Thu, 13 Dec 2007 19:01:28 +0300 Message-ID: <20071213160128.GA219@tv-sign.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: "Eric W. Biederman" Cc: Linux Containers , Andrew Morton , Pavel Emelyanov List-Id: containers.vger.kernel.org Sorry for the delay, and sorry, can't read this series carefully now. A couple of question though. On 12/12, Eric W. Biederman wrote: > > Currently task_active_pid_ns is not safe to call after a > task becomes a zombie and exit_task_namespaces is called, > as nsproxy becomes NULL. By reading the pid namespace from > the pid of the task we can trivially solve this problem Confused. If the task becomes a zombie, we can't assume it has a valid ->pids[].pid. The parent can release us as soon as exit_notify() drops tasklist. ? Oleg.