From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleg Nesterov Subject: Re: Signals to cinit Date: Mon, 10 Nov 2008 19:00:30 +0100 Message-ID: <20081110180030.GA12043@redhat.com> References: <20081101180505.GA24268@us.ibm.com> <20081110173839.GA11121@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20081110173839.GA11121-H+wXaHxf7aLQT0dZR+AlfA@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: sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org Cc: clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org, "Eric W. Biederman" , Containers , Nadia Derbey , Pavel Emelyanov List-Id: containers.vger.kernel.org On 11/10, Oleg Nesterov wrote: > > This way at least SIGKILL > always works. Forgot to mention... We must also change sig_ignored() to drop SIGKILL/SIGSTOP early when it comes from the same ns. Otherwise, it can mask the next SIGKILL from the parent ns. But this perhaps makes sense anyway, even without containers. Currently, when the global init has the pending SIGKILL, we can't trust __wait_event_killable/etc, and this is actually wrong. Oleg.