On Mon, Mar 11, 2002 at 10:40:44AM +0500, Sumit Agarwal wrote: > That is ofcourse a deadlock where everyone is running in a tight loop > on the processor. But remember once you go to sleep, the scheduler is > ready to run. Also you have to be sure that if you have disabled the > interrupts on the processor or not. If you are saying copy_to_user will > cause a deadlock, then I 'll say it will not. Check the code again for > it. I know what spinlocks are and do ;) And I still say that copy_to_user within a spinlock can trigger deadlock. (and it will once every while) -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
