Re: 995d11c4c0 ("drm: rework delayed connector cleanup in .."): WARNING: possible circular locking dependency detected

2017-12-18 Thread Maarten Lankhorst
Op 18-12-17 om 08:08 schreef Daniel Vetter: > Hm, the bisect looks funny. Only way I can explain that is that my > patch fixed a pre-existing lockdep splat, and uncovered the issue in > the ww-mutex self tests. That one is uncovered by the new > cross-release lockdep checks in 4.15. > > Anyway I

Re: 995d11c4c0 ("drm: rework delayed connector cleanup in .."): WARNING: possible circular locking dependency detected

2017-12-18 Thread Maarten Lankhorst
Op 18-12-17 om 08:08 schreef Daniel Vetter: > Hm, the bisect looks funny. Only way I can explain that is that my > patch fixed a pre-existing lockdep splat, and uncovered the issue in > the ww-mutex self tests. That one is uncovered by the new > cross-release lockdep checks in 4.15. > > Anyway I

Re: 995d11c4c0 ("drm: rework delayed connector cleanup in .."): WARNING: possible circular locking dependency detected

2017-12-17 Thread Daniel Vetter
Hm, the bisect looks funny. Only way I can explain that is that my patch fixed a pre-existing lockdep splat, and uncovered the issue in the ww-mutex self tests. That one is uncovered by the new cross-release lockdep checks in 4.15. Anyway I think this is an issue with the ww-mutex tests, not my

Re: 995d11c4c0 ("drm: rework delayed connector cleanup in .."): WARNING: possible circular locking dependency detected

2017-12-17 Thread Daniel Vetter
Hm, the bisect looks funny. Only way I can explain that is that my patch fixed a pre-existing lockdep splat, and uncovered the issue in the ww-mutex self tests. That one is uncovered by the new cross-release lockdep checks in 4.15. Anyway I think this is an issue with the ww-mutex tests, not my