> If we do this then kick_iocb() has only one in-kernel caller, in > drivers/usb/gadget/inode.c. I wonder if the gadget code really needs > to be using kick_iocb()? I don't think that it needs to, no. It's only using the aio retry functionality to perform a copy of read data into user space. I have a patch to switch it to using schedule_work() instead: http://marc.info/?l=linux-fsdevel&m=125624446623075&w=2 I've been focusing on other things instead of pushing that to the usb folks to be tested and merged, though. I've cc:ed them in case they want to run with this. - z -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
