Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269466AbUJFUbK (ORCPT ); Wed, 6 Oct 2004 16:31:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269460AbUJFU2w (ORCPT ); Wed, 6 Oct 2004 16:28:52 -0400 Received: from clock-tower.bc.nu ([81.2.110.250]:48043 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S269484AbUJFU0O (ORCPT ); Wed, 6 Oct 2004 16:26:14 -0400 Subject: Re: UDP recvmsg blocks after select(), 2.6 bug? From: Alan Cox To: Andries Brouwer Cc: Joris van Rantwijk , Linux Kernel Mailing List In-Reply-To: <20041006193053.GC4523@pclin040.win.tue.nl> References: <1097080873.29204.57.camel@localhost.localdomain> <20041006193053.GC4523@pclin040.win.tue.nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1097090625.29707.9.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 06 Oct 2004 20:23:46 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1162 Lines: 30 On Mer, 2004-10-06 at 20:30, Andries Brouwer wrote: > A descriptor shall be considered ready for reading when a > call to an input function with O_NONBLOCK clear would not > block, whether or not the function would transfer data > successfully. (The function might return data, an end-of- > file indication, or an error other than one indicating > that it is blocked, and in each of these cases the > descriptor shall be considered ready for reading.) > > As far as I can interpret these sentences, Linux does not conform. Nor does anything else in that case. I guess we need a POSIX_ME_HARDER socket option. As to the Stevens reference - Stevens says nothing about read but does mention the problem of accept, which is one of the "can't fix" type examples. Connection setup pending select returns Connection destroyed accept blocks Alan - 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/