On Mon, Dec 11, 2017 at 10:19:28AM +0100, Daniel Vetter wrote: > On Fri, Dec 08, 2017 at 11:54:19AM +0100, Peter Zijlstra wrote: > > On Thu, Dec 07, 2017 at 11:08:49AM +0100, Daniel Vetter wrote: > > > Since -rc1 we're hitting a bunch of lockdep splats using the new > > > cross-release stuff around the 2 kthread completions. In all cases > > > they are because totally independent uses of kthread are mixed up by > > > lockdep into the same locking class, creating artificial deadlocks. > > > > > > Fix this by converting kthread code in the same way as e.g. > > > alloc_workqueue already works: Use macros for the public api so we can > > > have a callsite specific lockdep key, then pass that through the > > > entire callchain. Due to the many entry points this is slightly > > > tedious. > > > > > > Cc: Tvrtko Ursulin <[email protected]> > > > Cc: Marta Lofstedt <[email protected]> > > > Cc: Byungchul Park <[email protected]> > > > Cc: Ingo Molnar <[email protected]> > > > Cc: Peter Zijlstra <[email protected]> > > > Cc: Tejun Heo <[email protected]> > > > Cc: Kees Cook <[email protected]> > > > Cc: Thomas Gleixner <[email protected]> > > > Cc: Shaohua Li <[email protected]> > > > Cc: Andrew Morton <[email protected]> > > > Cc: Jens Axboe <[email protected]> > > > Cc: Daniel Vetter <[email protected]> > > > Cc: Greg Kroah-Hartman <[email protected]> > > > Cc: Jonathan Corbet <[email protected]> > > > Cc: Oleg Nesterov <[email protected]> > > > References: https://bugs.freedesktop.org/show_bug.cgi?id=103950 > > > Signed-off-by: Daniel Vetter <[email protected]> > > > > Acked-by: Peter Zijlstra (Intel) <[email protected]> > > Who's going to pick this up? Ingo, Andrew?
This didn't seem to have made it into -rc4. Anything needed to get it going? Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
