Re: [PATCH] aio_run_iocb should always retry

On Tuesday 24 July 2007, Sarah Sharp wrote:
> The problem comes when someone calls sys_io_cancel() on a read.  If the
> retry function has started before this point, everything is fine.
> However, if sys_io_cancel() runs before the retry function, aio_run_iocb
> will notice the iocb is cancelled and call aio_complete instead.  The
> retry function never runs, and the data structures are never freed.

I certainly recall a lot of headscratching about those cancelation
paths ... so I'm not surprised to hear about some issues there.
At this point I'd not care to guess if that's a "new" issue or not.
(That is, there have been AIO changes that weren't fully compatible,
and didn't include gadgetfs updates.)

So to the AIO team:  does Sarah's analysis seem correct to you?

- Dave



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel