There are a ton of false lockdep splats that were introduced with commit 2dcd5adfb740: "locking/lockdep: Remove the BROKEN flag from CONFIG_LOCKDEP_CROSSRELEASE and CONFIG_LOCKDEP_COMPLETIONS". I'm seeing this triggered by a number of xfstests tests, including shared/298. I see there was some discussion about this here: https://www.spinics.net/lists/linux-xfs/msg10832.html ... but I don't see any solution yet. Is anyone working on this? Failing that can we please make the completion lockdep something which is optional since the false positives are incredibly !@#@!?! annoying? That way I can still use most of lockdep, instead of being forced to completely disable lockdep? Thanks, - Ted -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
