Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760766AbXFRAnj (ORCPT ); Sun, 17 Jun 2007 20:43:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752851AbXFRAna (ORCPT ); Sun, 17 Jun 2007 20:43:30 -0400 Received: from gate.crashing.org ([63.228.1.57]:44725 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751773AbXFRAna (ORCPT ); Sun, 17 Jun 2007 20:43:30 -0400 Subject: Re: And now for something _totally_ different: Linux v2.6.22-rc5 From: Benjamin Herrenschmidt To: Davide Libenzi Cc: Nicholas Miell , Linus Torvalds , Linux Kernel Mailing List , Oleg Nesterov In-Reply-To: References: <1182064500.2798.6.camel@entropy> <1182108399.3794.4.camel@entropy> <1182125303.3794.8.camel@entropy> Content-Type: text/plain Date: Mon, 18 Jun 2007 10:43:11 +1000 Message-Id: <1182127391.26853.207.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: 871 Lines: 25 On Sun, 2007-06-17 at 17:20 -0700, Davide Libenzi wrote: > > > > I didn't see anything like that in linux.git, missed Ben's patch to > the > > list, and mixed up your description with the original TIF_SIGPENDING > > work. > > They will still race on the signal queue though. That is, if you > create a > signalfd and three threads are doing a read(2) over it, if a signal > is > sent to the thread group (tsk->signal->shared_pending), only one will > fetch the signal. I think that's the correct behaviour anyway. > Andrew or Linus, did you get Ben's patch? It might have been missed... I can resend later today. 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/