Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758117AbXFTRi1 (ORCPT ); Wed, 20 Jun 2007 13:38:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754501AbXFTRiT (ORCPT ); Wed, 20 Jun 2007 13:38:19 -0400 Received: from smtp2.linux-foundation.org ([207.189.120.14]:42647 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751475AbXFTRiT (ORCPT ); Wed, 20 Jun 2007 13:38:19 -0400 Date: Wed, 20 Jun 2007 10:38:04 -0700 (PDT) From: Linus Torvalds To: Oleg Nesterov cc: Benjamin Herrenschmidt , Davide Libenzi , Nicholas Miell , Linux Kernel Mailing List Subject: Re: Fix signalfd interaction with thread-private signals In-Reply-To: <20070620111415.GA91@tv-sign.ru> Message-ID: References: <1182108399.3794.4.camel@entropy> <1182125303.3794.8.camel@entropy> <1182127391.26853.207.camel@localhost.localdomain> <20070619091452.GA94@tv-sign.ru> <1182254988.26853.334.camel@localhost.localdomain> <20070619140646.GB27343@tv-sign.ru> <1182295473.26853.386.camel@localhost.localdomain> <20070620111415.GA91@tv-sign.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 773 Lines: 26 On Wed, 20 Jun 2007, Oleg Nesterov wrote: > > Also, suppose that some thread does > > for (;;) > signal(SIGSEGV, SIG_IGN); > > Now we have the same situation. do_sigaction() can steal SIGSEGV from > another thread. Actually, that shouldn't be possible. See "force_sig_info()". It does not allow blocking or ignoring forced signals. We will reset such a signal handler to SIG_DFL, and unlock it. So if you get a SIGSEGV while SIGSEGV's are blocked or ignored, the kernel *will* kill you. No questions asked. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/