From mboxrd@z Thu Jan 1 00:00:00 1970 From: sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org Subject: Re: [PATCH 3/3] Signal semantics for pid namespaces Date: Mon, 3 Sep 2007 09:59:16 -0700 Message-ID: <20070903165916.GD2793@us.ibm.com> References: <20070831203834.GC3268@us.ibm.com> <20070901114803.GA215@tv-sign.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20070901114803.GA215-6lXkIZvqkOAvJsYlp49lxw@public.gmane.org> 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: Oleg Nesterov Cc: Containers , Pavel Emelianov List-Id: containers.vger.kernel.org Oleg Nesterov [oleg-6lXkIZvqkOAvJsYlp49lxw@public.gmane.org] wrote: | On 08/31, sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org wrote: | > | > @@ -48,7 +49,7 @@ static int sig_init_ignore(struct task_s | > if (likely(!is_container_init(tsk->group_leader))) | > return 0; | > | > - if (!in_interrupt()) | > + if (is_current_in_ancestor_pid_ns(tsk) && !in_interrupt()) | > return 0; | | We should return 1 in that case, afaics the logic is wrongly reversed. Hmm. My unit tests worked as I thought they should :-) return 1 implies we "ignore the signal" right ? If the signal is from an ancestor namespace, and we are not in interrupt context, we don't want to ignore the signal. no ? | | Oleg.