Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269318AbUJFRoA (ORCPT ); Wed, 6 Oct 2004 13:44:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269157AbUJFRn7 (ORCPT ); Wed, 6 Oct 2004 13:43:59 -0400 Received: from clock-tower.bc.nu ([81.2.110.250]:21931 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S269337AbUJFRnt (ORCPT ); Wed, 6 Oct 2004 13:43:49 -0400 Subject: Re: UDP recvmsg blocks after select(), 2.6 bug? From: Alan Cox To: Joris van Rantwijk Cc: Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1097080873.29204.57.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 06 Oct 2004 17:41:16 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 15 On Mer, 2004-10-06 at 15:52, Joris van Rantwijk wrote: > My understanding of POSIX is limited, but it seems to me that a read call > must never block after select just said that it's ok to read from the > descriptor. So any such behaviour would be a kernel bug. Select indicates there may be data. That is all - it might also be an error, it might turn out to be wrong. You should always combine select with nonblocking I/O - 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/