From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-2 Description of problem: Calling of aio_read() before aio_write() on the socket leads to "in progress" state of both requests, whereas calling of aio_write() before aio_read() leads to successful completion of write request and "in progress" state of read request. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create pair of connected stream or datagram sockets. 2. Call aio_read() with correct buffer/length and none notification. 3. Call aio_write() with correct data/length and none notification. Actual Results: Data are not sent. aio_error() returns EINPROGRESS for both requests. Expected Results: Data should be sent, aio_error() should return 0 for write request and EINPROGRESS for read request. Additional info:
Created attachment 119885 [details] Test reproducing the problem
The aio_* functions operate on files, not sockets, pipes, or whatever else. The implementation works correctly for files.