2665 2012-06-27 03:26:57 +0000 POSIX: case aio_return 2-1 3-2 4-1 return UNRESOLVED on all arches 2012-07-31 08:26:12 +0000 1 1 7 Build System, Metadata & Runtime Meta-yocto meta-yocto 1.3 x86 Multiple VERIFIED NOTABUG Undecided enhancement 1.3 M2 2332 1 kai.kang kai.kang laurentiu.serban poky.bs.watcher poky.watcher zhenfeng.zhao --- --- --- oldest_to_newest 22615 0 kai.kang 2012-06-27 03:26:57 +0000 case aio_return 2-1 3-2 4-1 return UNRESOLVED on all arches case 2-1 and 3-2 call aio_return 2 times and expect return -1 case 4-1 call aio_return with argument aiocbp which does not point at a control block for an asynchronous I/O request, and expect error EINVAL 22617 1 kai.kang 2012-06-27 03:34:17 +0000 For case 2-1 3-2, they test call aio_return 2 times and expect return -1. In the POSIX spec, it says: The aio_return( ) function may be called exactly once to retrieve the return status of a given asynchronous operation; thereafter, if the same aiocb structure is used in a call to aio_return( ) or aio_error( ), an error *may* be returned. It just says "may" and not compel to return an error, so it is implement dependent and I think they are not bugs. --------------------------------------------- For case 4-1, the spec says: The aio_return() function *may* fail if: [EINVAL] The aiocbp argument does not refer to an asynchronous operation whose return status has not yet been retrieved. This is also 'may' and is implement dependent and not a bug. 23631 2 laurentiu.serban 2012-07-31 08:26:12 +0000 Setting to Verified after last comment