From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261408AbVFMHZ2 (ORCPT ); Mon, 13 Jun 2005 03:25:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261338AbVFMHZ2 (ORCPT ); Mon, 13 Jun 2005 03:25:28 -0400 Received: from gate.crashing.org ([63.228.1.57]:3278 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S261408AbVFMHZZ (ORCPT ); Mon, 13 Jun 2005 03:25:25 -0400 Subject: Re: Add pselect, ppoll system calls. From: Benjamin Herrenschmidt To: Linus Torvalds Cc: jnf , Alan Cox , David Woodhouse , Linux Kernel Mailing List , akpm@osdl.org, drepper@redhat.com In-Reply-To: References: <1118444314.4823.81.camel@localhost.localdomain> <1118616499.9949.103.camel@localhost.localdomain> Content-Type: text/plain Date: Mon, 13 Jun 2005 17:23:21 +1000 Message-Id: <1118647401.5986.91.camel@gaston> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > One pretty simple alternative is to just make the timeout be a global, and > have the signal handler clear it, guaranteeing that if we're just about to > hit the select(), we'll exit immediately. That is still racy ... if the signal hits between loading that global to to pass it to select and the actual syscall entry ... pretty narrow but still there.