Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269280AbUJQT0q (ORCPT ); Sun, 17 Oct 2004 15:26:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269284AbUJQT0q (ORCPT ); Sun, 17 Oct 2004 15:26:46 -0400 Received: from sj-iport-2-in.cisco.com ([171.71.176.71]:10502 "EHLO sj-iport-2.cisco.com") by vger.kernel.org with ESMTP id S269280AbUJQT0g convert rfc822-to-8bit (ORCPT ); Sun, 17 Oct 2004 15:26:36 -0400 Reply-To: From: "Hua Zhong" To: , , "'Linux-Kernel@Vger. Kernel. Org'" Subject: RE: UDP recvmsg blocks after select(), 2.6 bug? Date: Sun, 17 Oct 2004 12:26:30 -0700 Organization: Cisco Systems Message-ID: <012c01c4b47f$345071b0$b83147ab@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 8BIT X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 Importance: Normal Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 788 Lines: 20 > I'm sorry, that's an absolutely preposterous view. For > one thing, Linux violates this by allowing processes and > threads to share file descriptors (since another process > can steal the data before the call to 'recvmsg'). Oh > well, I guess we'll have to take that out if we want to > comply with POSIX on 'select' semantics. Another typical fake argument. Do not mix kernel and user space problems. The standard says the [following] recvmsg would not block, not the following recvmsg *from the same* thread would not block. Hua - 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/