[PATCH v5] lib/spinlock_debug.c: prevent a recursive cycle in the debug code

From: Byungchul Park
Date: Fri Jan 29 2016 - 07:44:07 EST


changes from v4 to v5
- found out a clear scenario which make a system crazy. at least it
should not be caused by the debug code.

changes from v3 to v4
- reuse a existing code as much as possible for preventing an infinite
recursive cycle.

changes from v2 to v3
- avoid printk() only in case of lockup suspected, not real lockup in
which case it does not help at all.
- consider not only console_sem.lock but also logbuf_lock which is used
by printk().

changes from v1 to v2
- only change comment and commit message esp. replacing "deadlock" with
"infinite recursive cycle", since it is not an actual deadlock.

thanks,
byungchul

-----8<-----