Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 15 Oct 2002 19:02:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 15 Oct 2002 19:02:16 -0400 Received: from x35.xmailserver.org ([208.129.208.51]:1942 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id ; Tue, 15 Oct 2002 18:51:48 -0400 X-AuthUser: davidel@xmailserver.org Date: Tue, 15 Oct 2002 16:05:49 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@blue1.dev.mcafeelabs.com To: John Gardiner Myers cc: Benjamin LaHaise , Dan Kegel , Shailabh Nagar , linux-kernel , linux-aio , Andrew Morton , David Miller , Linus Torvalds , Stephen Tweedie Subject: Re: [PATCH] async poll for 2.5 In-Reply-To: <3DAC9859.5060005@netscape.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 919 Lines: 23 On Tue, 15 Oct 2002, John Gardiner Myers wrote: > Nonetheless, the requirement for user space to test the condition after > the registration, not before, is subtle. A program which does these in > the wrong order is still likely to pass QA and will fail in production > in a way that will be difficult to diagnose. There is no rational > reason for the kernel to not test the condition upon registration. All APIs have their own specifications and if you do not follow them, or you're using a different interfacing just because the name looks similar to other APIs, you're going to have problems. The problem it's not inside the API but inside the user ... - Davide - 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/