On Thu, Jan 20, 2011 at 10:31 AM, Trond Myklebust <Trond.Myklebust@xxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
