[PATCH] Make debugging variant of spinlocks a bit more robust
From: Petr Vandrovec <vandrove@vc.cvut.cz> While I was trying to hunt down problem with spin_lock_irq in send_sig_info, I noticed that debugging spinlocks are a bit unusable. The problem is that these spinlocks first print warning, and then decrement babble. So if the lock is used by printk code (like runqueue lock was), we get nothing, just a lockup or a double fault... When we first decrement babble and then print the error message we can break this unfortunate situation and the error message (5 of the same...) appear on screen.
Showing
Please register or sign in to comment