From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L0HDY-0004LA-8D for qemu-devel@nongnu.org; Wed, 12 Nov 2008 10:01:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L0HDV-0004K8-JV for qemu-devel@nongnu.org; Wed, 12 Nov 2008 10:01:15 -0500 Received: from [199.232.76.173] (port=56652 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L0HDV-0004K1-EH for qemu-devel@nongnu.org; Wed, 12 Nov 2008 10:01:13 -0500 Received: from mx2.redhat.com ([66.187.237.31]:44536) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L0HDV-0007uZ-0z for qemu-devel@nongnu.org; Wed, 12 Nov 2008 10:01:13 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id mACF19rX016689 for ; Wed, 12 Nov 2008 10:01:09 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id mACF19Hb012139 for ; Wed, 12 Nov 2008 10:01:09 -0500 Received: from zweiblum.travel.kraxel.org (vpn-4-32.str.redhat.com [10.32.4.32]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id mACF1777018576 for ; Wed, 12 Nov 2008 10:01:08 -0500 Message-ID: <491AEFB2.8040302@redhat.com> Date: Wed, 12 Nov 2008 16:01:06 +0100 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [patch] Fix block I/O hang. References: <4919B46C.3040804@redhat.com> <4919B79A.5030402@codemonkey.ws> <4919C550.5020609@redhat.com> <20081112134902.GA4014@linuxtv.org> In-Reply-To: <20081112134902.GA4014@linuxtv.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Johannes Stezenbach wrote: > I don't know what kind of fd you're talking about, but the > Linux select man page says: pipe. > BUGS > Under Linux, select() may report a socket file descriptor as "ready = for > reading", while nevertheless a sub=E2=80=90 sequent read blocks. Th= is could for > example happen when data has arrived but upon examination has wro= ng > checksum and is discarded. There may be other circumstances i= n which > a file descriptor is spuriously reported as ready. Thus it may be s= afer to > use O_NONBLOCK on sockets that should not block. Unlikely to apply here, I've also found the real problem (see other mail in this thread). cheers, Gerd