Re: kern/45441: aio_write and aio_read connected to one pipe don't make progress

[David Laight <david%l8s.co.uk@localhost>]

The following reply was made to PR kern/45441; it has been noted by GNATS.

From: David Laight <david%l8s.co.uk@localhost>
To: Alexander Nasonov <alnsn%yandex.ru@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/45441: aio_write and aio_read connected to one pipe don't 
make progress
Date: Thu, 13 Oct 2011 21:47:30 +0100

 On Wed, Oct 12, 2011 at 09:26:40PM +0100, Alexander Nasonov wrote:
 > alnsn%NetBSD.org@localhost wrote:
 > > If you initialize two aiocb structs to connect to one pipe and call 
 > > aio_read before aio_write, then aio_error() calls will always be returning 
 > > EINPROGRESS.
 > ...
 > >Fix:
 > > not known
 > 
 > The best fix, I think, is return ESPIPE for non-seekable fildes rather
 > than silently ignoring aio_offset. This would indirectly solve the issue
 > described in this PR.
 
 IIRC that breaks historic practise.
 
 The likely fubar here is that 'aio' is synchronous on a single kernel
 thread.
 
        David
 
 -- 
 David Laight: david%l8s.co.uk@localhost