On Mon, 2016-06-20 at 22:02 -0600, David Ahern wrote: > I just updated to top of next-net tree (697666eac66) and still seeing an > occasional lockdep splat. It is not reliable to the point I would > attempt a git bisect. 2 splats -- 1 for ipv4 (first login to VM after > boot) and ipv6 (second login to VM after boot). Perhaps it is more > fallout of the packet scheduling changes you have been making this > iteration. Just a guess based on sch_direct_xmit in both traces.
Seems to be a lockdep hash chain collision, please report to lkml.
