On Thu, 2006-02-16 at 17:12 +0000, Russell King wrote: > This is probably an idiotic question, but if there's something in the > scsi release handler can't be called in non-process context, why can't > scsi queue up the release processing via the work API itself, rather > than having to have this additional code and complexity for everyone?
It's because, in order to get a guaranteed single allocation for the workqueue to execute in user context, I need to know when the release will be called. The only way to do that is to add the execute in process context directly to kref_put. James ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
