On Thu, Dec 14, 2017 at 12:38:52PM -0500, Steven Rostedt wrote: > > Currently, when lockdep detects a possible deadlock scenario that involves 3 > or more levels, it just shows the chain, and a CPU sequence order of the > first and last part of the scenario, leaving out the middle level and this > can take a bit of effort to understand. By adding a third level, it becomes > easier to see where the deadlock is.
So is anybody actually using this? This (together with the callchain for #0) is always the first thing of the lockdep output I throw away.
