On Thu, Jul 14, 2016 at 04:45:52PM +0200, Daniel Vetter wrote: > On Thu, Jul 14, 2016 at 01:47:49PM +0300, Mika Kuoppala wrote: > > Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: > > > > > Since the suspend_work can arm itself if the console_lock() is currently > > > held elsewhere, simply calling flush_work() doesn't guarantee that the > > > work is idle upon return. To do so requires using cancel_work_sync(). > > > > > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > > Cc: Daniel Vetter <daniel.vetter@xxxxxxxx> > > > Cc: Mika Kuoppala <mika.kuoppala@xxxxxxxxx> > > > > Reviewed-by: Mika Kuoppala <mika.kuoppala@xxxxxxxxx> > > Cc: stable@xxxxxxxxxxxxxxx I presume? Checking for this should be part of > the review ... No known bug - unlikely since ~nobody unloads the module. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
