Hello, > I wrote a sample module which looked like this and i expected the module to > hang as i have used 2 spin_lock simultaneously. But i find the print after > the second spin_lock being printed and the module works perfectly fine. Can > any body please help me in understanding this? I got this problem from a > driver i wrote and had a typo "spin_lock" instead of "spin_unlock" the > driver worked fine and i caught the mistake only during a review Are you running your tests on an UP with preemption disabled? thanks, Daniel. _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
