Re: [PATCH 2.5.71-mm1] aio process hang on EINVAL

[jgmyers@netscape.com (John Myers)]

[-- Attachment #1: Type: text/plain, Size: 615 bytes --]

Daniel McNeil wrote:

>I prefer getting the error on io_submit.
>  
>
I prefer getting the error on io_getevents().  The code that handles the 
output of io_getevents() already has to handle per-operation errors.  
The only thing user space can reasonably do with errors returned by 
io_submit() is to retry or assert.  Anything else would duplicate logic 
that already has to be in and is better handled by the code that handles 
the output io_getevents().

io_submit() should only return errors in cases where the caller is 
obviously buggy/malicious or in cases where it is not possible to 
generate an event.



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3941 bytes --]