Return-Path: Received: from mail-wy0-f174.google.com ([74.125.82.174]:42016 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753599Ab1ASXhi (ORCPT ); Wed, 19 Jan 2011 18:37:38 -0500 In-Reply-To: <1295479900.22151.19.camel@heimdal.trondhjem.org> References: <20110119223543.30706.10304.stgit@matisse.1015granger.net> <1295479517.22151.16.camel@heimdal.trondhjem.org> <1295479900.22151.19.camel@heimdal.trondhjem.org> Date: Thu, 20 Jan 2011 10:37:35 +1100 Message-ID: Subject: Re: [PATCH] NFS: Fix "BUG at fs/aio.c:554!" From: Nick Piggin To: Trond Myklebust Cc: Chuck Lever , linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org, wen.gang.wang@oracle.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-nfs-owner@vger.kernel.org List-ID: MIME-Version: 1.0 On Thu, Jan 20, 2011 at 10:31 AM, Trond Myklebust wrote: > On Thu, 2011-01-20 at 10:26 +1100, Nick Piggin wrote: >> On Thu, Jan 20, 2011 at 10:25 AM, Trond Myklebust >> > Also, why is EIO the correct reply when no bytes were read/written? Why >> > shouldn't the VFS aio code be able to cope with a zero byte reply? >> >> What would it do? > > Just return that zero byte reply to userland. > > zero bytes is a valid reply for ordinary read() and write(), so why > should we have to do anything different for aio_read()/aio_write()? It doesn't give userspace much to do. zero reply from read means EOF. Zero reply from write is pretty useless, I don't think we do it in the buffered write path -- we either ensure we write at least something or have a meaningful error to return.