Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933925AbXFFAPp (ORCPT ); Tue, 5 Jun 2007 20:15:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1764245AbXFFAPi (ORCPT ); Tue, 5 Jun 2007 20:15:38 -0400 Received: from rwcrmhc13.comcast.net ([204.127.192.83]:55633 "EHLO rwcrmhc13.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763761AbXFFAPh (ORCPT ); Tue, 5 Jun 2007 20:15:37 -0400 Subject: Re: [PATCH/RFC] signal races/bugs, losing TIF_SIGPENDING and other woes From: Nicholas Miell To: Davide Libenzi Cc: Benjamin Herrenschmidt , Linus Torvalds , Linux Kernel list , Andrew Morton , Paul Mackerras In-Reply-To: References: <1181006711.31677.97.camel@localhost.localdomain> <1181009413.31677.117.camel@localhost.localdomain> <1181013756.31677.123.camel@localhost.localdomain> <1181023787.2785.14.camel@entropy> <1181028453.31677.127.camel@localhost.localdomain> <1181087462.2788.8.camel@entropy> Content-Type: text/plain Date: Tue, 05 Jun 2007 17:15:36 -0700 Message-Id: <1181088936.2788.10.camel@entropy> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 (2.10.1-4.fc7.0.njm.1) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1115 Lines: 29 On Tue, 2007-06-05 at 17:11 -0700, Davide Libenzi wrote: > On Tue, 5 Jun 2007, Nicholas Miell wrote: > > > Yes, that's certainly wrong, but that's an implementation issue. I was > > more concerned about the design of the API. > > > > Naively, I would expect a reads on a signalfd to return either process > > signals or thread signals targeted towards the thread doing the read. > > > > What it actually does (delivering process signals or thread signals > > targeted towards the thread that created the signalfd) is weird. > > > > For one, it means you can't create a single signalfd, stick it in an > > epoll set, and then wait on that set from multiple threads. > > In your box threads do share the sighand, don't they? :) > I have no idea what you're trying to say, but it doesn't appear to address the issue I raise. -- Nicholas Miell - 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/