Let me ask a potentially stupid question, Can someone give an example of the problem this completion lockdep is actually trying to *catch*. The lockdep message is sufficiently confusing it's not even clear what *good* it is in the first place. Is there an example of a bug that this lockdep feature hasf actually caught in real life, as opposed to false positives? - Ted
