Steven Rostedt, Red Hat

Ever since lockdep was introduced in 2006, most deadlock scenarios have been avoided. But when lockdep does detect a problem with the locking, the output it gives can be very cryptic and hard to understand, especially when the locking issues have to do with interrupts or del_timer_sync().

This talk will explain how to translate the lockdep output so that you can understand the locking problem scenario and confidently fix your code (or someone else’s code) to avoid any deadlocks.