From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57058) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4Rl8-0008La-27 for qemu-devel@nongnu.org; Wed, 09 Nov 2016 07:13:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4Rl3-0006oT-40 for qemu-devel@nongnu.org; Wed, 09 Nov 2016 07:13:42 -0500 Received: from mx3-phx2.redhat.com ([209.132.183.24]:50459) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c4Rl2-0006nx-S1 for qemu-devel@nongnu.org; Wed, 09 Nov 2016 07:13:37 -0500 Date: Wed, 9 Nov 2016 07:13:35 -0500 (EST) From: Paolo Bonzini Message-ID: <1691321903.11658231.1478693615012.JavaMail.zimbra@redhat.com> In-Reply-To: References: <1478075542-18904-1-git-send-email-pbonzini@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PULL v3 00/30] Misc patches for 2016-10-31 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: Max Reitz , qemu-devel@nongnu.org > but then fails the assertion, which means read_sync() is returning 0 in > our particular test (which sort of makes sense: the test is purposefully > truncating the server stream at various points to see how the client > reacts). I'm trying to figure out if always treating early EOF as a > read error would be sufficient to make things work the way we want in > the client. Yeah, early EOF should become ESHUTDOWN, ECONNRESET or similar. Paolo