Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759106AbXFSMKW (ORCPT ); Tue, 19 Jun 2007 08:10:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757149AbXFSMKI (ORCPT ); Tue, 19 Jun 2007 08:10:08 -0400 Received: from gate.crashing.org ([63.228.1.57]:36361 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757110AbXFSMKG (ORCPT ); Tue, 19 Jun 2007 08:10:06 -0400 Subject: Re: Fix signalfd interaction with thread-private signals From: Benjamin Herrenschmidt To: Oleg Nesterov Cc: Linus Torvalds , Davide Libenzi , Nicholas Miell , Linux Kernel Mailing List In-Reply-To: <20070619091452.GA94@tv-sign.ru> References: <1182064500.2798.6.camel@entropy> <1182108399.3794.4.camel@entropy> <1182125303.3794.8.camel@entropy> <1182127391.26853.207.camel@localhost.localdomain> <20070619091452.GA94@tv-sign.ru> Content-Type: text/plain Date: Tue, 19 Jun 2007 22:09:48 +1000 Message-Id: <1182254988.26853.334.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 831 Lines: 21 On Tue, 2007-06-19 at 13:14 +0400, Oleg Nesterov wrote: > The commited "Fix signalfd interaction with thread-private signals" > (commit caec4e8dc85e0644ec24aeb36285e1ba02da58cc) doesn't implement > this. Indeed, if you want what Davide described, you need to also change signalfd side. The patch I did merely prevents another thread from dequeuing somebody else private signals. As it stands, signalfd will still try it... and only get the shared ones. It will not however get the private signals of the caller if it is different from the context associated with the signalfd. Ben. - 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/