On Thu, May 01, 2014 at 07:53:58AM +0200, Ricardo Ribalda Delgado wrote: > Thanks for your comments. This fix does not avoid the task being > killed (which is not an error). What it does is that IF the task is > killed or we are out of memory we will exit with all the resources > properly released and no locks helds, giving the user a chance to > reload/rebind the module instead of getting and unstable system that > cannot even reboot without a powercycle. How does it ensure that? What's to stop the task being killed after we check to see if the task was killed.
Attachment:
signature.asc
Description: Digital signature
