timer: Try to survive timer callback preempt_count leak
authorThomas Gleixner <tglx@linutronix.de>
Fri, 12 Mar 2010 19:13:23 +0000 (20:13 +0100)
committerThomas Gleixner <tglx@linutronix.de>
Fri, 12 Mar 2010 21:40:44 +0000 (22:40 +0100)
commit802702e0c2618465b813242d4dfee6a233ba0beb
treee21c74065e82a77c45c4f815c626fbafc7fff469
parent576da126a6c7364d70dfd58d0bbe43d05cf5859f
timer: Try to survive timer callback preempt_count leak

If a timer callback leaks preempt_count we currently assert a
BUG(). That makes it unnecessarily hard to retrieve information about
the problem especially on laptops and headless stations.

There is a decent chance to survive the preempt_count leak by
restoring the preempt_count to the value before the callback. That
allows in many cases to get valuable information about the root cause
of the problem.

We carried that fixup in preempt-rt for years and were able to decode
such wreckage quite a few times.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Arjan van de Veen <arjan@infradead.org>
kernel/timer.c