Jacek Caban jacek@codeweavers.com writes:
Although (at least now) all read and write implementations always queue async on success, it's not the case for ioctl. I think we should allow simple ioctls without pending results to not care about explicitly handling async objects, but those still need a queued async for proper result reporting. We currently don't set events, queue APCs nor send completion for them.
My initial thought was to make async object work better without associated queue, but that leads to problems with references from an async to fd.
I think that would be better than creating a dummy queue.