On Tue, Dec 28, 2010 at 2:24 PM, Felipe Contreras <felipe.contreras@xxxxxxxxx> wrote: > user-space crashed, not kernel-space; the code would continue to run > and eventually release the lock. So you'll have to be more specific about the scenario you are describing. If there's a user thread that is still running the proc_*_dma() function, and we agree that this thread keeps running until completion and then returns to user space, what's the problem ? If that user thread will crash, drv_remove_all_resources() will clean up all map_obj's. > Yeah, so the chances of getting this fixed on 2.6.37 are dimmed. I wouldn't worry about that.. In the worst case, "Cc: stable@xxxxxxxxxx" will push the fix into 2.6.37.x.. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
