Thread (1 message) 1 message, 1 author, 2015-03-18

Re: aio_return(3): misleading RETURN VALUE

From: Stéphane Aulery <hidden>
Date: 2015-03-18 12:14:47

Hello Alexander,

Le mercredi 18 mars 2015 à 09:03:38, Alexander Holler a écrit :
I suggest to use the same wording as in write(2) in the paragraph RETURN
VALUE:

"On error, -1 is returned, and errno is set appropriately."
Like that ?

    If the asynchronous I/O operation has completed, this function
    returns the value that would have been returned in case of a
    synchronous read(2), write(2), fsync(2) or fdatasync(2), call. On
    error, -1 is returned, and errno is set appropriately.

    If the asynchronous I/O operation has not yet completed, the return
    value and effect of aio_return() are undefined.

I think that's what you meant. What will happen if the asynchronous I/O
operation has not yet completed please ?

Regards,

-- 
Stéphane Aulery
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help