Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757880AbXFTB0M (ORCPT ); Tue, 19 Jun 2007 21:26:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757778AbXFTBZ6 (ORCPT ); Tue, 19 Jun 2007 21:25:58 -0400 Received: from gate.crashing.org ([63.228.1.57]:59869 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757102AbXFTBZ6 (ORCPT ); Tue, 19 Jun 2007 21:25:58 -0400 Subject: Re: Fix signalfd interaction with thread-private signals From: Benjamin Herrenschmidt To: Davide Libenzi Cc: Oleg Nesterov , Linus Torvalds , Nicholas Miell , Linux Kernel Mailing List In-Reply-To: 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: Wed, 20 Jun 2007 11:25:39 +1000 Message-Id: <1182302739.22337.9.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: 943 Lines: 25 On Tue, 2007-06-19 at 16:49 -0700, Davide Libenzi wrote: > Actually, I think signalfd is fine as is, with Ben's patch applied. > Signalfd should only fetch shared signals, not specific ones (in any > case). The only advantage of that additional patch is that it will allow any thread to fetch its own private signals via signalfd, regardless of what context is attached to the signalfd in the first place. Without the patch (with what's currently in Linus tree), a thread will only get its own private signals if it's also the thread that created the signalfd (and thus is attached to the signalfd "context"). I don't mind either way, up to you guys to decide what semantics you want. 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/