> No, this does not sound right. This works around the symptoms. How so? The test looks clearly wrong to me. aio_suspend will return when the CB0 request is done, and the CB1 request is still outstanding. Unless we synchronize with that request, CB1 is still in the aio data structures when it is no longer live on the stack.