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 <[email protected]>
Cc: Linux Torvalds <[email protected]>
Cc: Andrew Morton <[email protected]>
Cc: Arjan van de Veen <[email protected]>

0 files changed, 0 insertions, 0 deletions