* Bart Van Assche <[email protected]> wrote:
> On Fri, 2019-04-12 at 07:47 +0200, Ingo Molnar wrote:
> > So why don't we add a debug_locks test to lockdep_unregister_key()
> > instead? The general principle to bring lockdep to a screeching halt when
> > bugs are detected, ASAP.
>
> Hi Ingo,
>
> Since this issue was introduced by patch "locking/lockdep: Zap lock classes
> even with lock debugging disabled" and since that patch is in the tip tree
> but not yet upstream: do you prefer that I post a version 3 of that patch or
> do you rather prefer that I post a follow-up patch?
The crash fix is now upstream, mind sending a followup patch for the
warning fix?
Thanks,
Ingo
