On Thu, Oct 29, 2015 at 11:24:47AM +0900, Tejun Heo wrote: > Hello, > > That's weird. > > On Wed, Oct 28, 2015 at 08:57:28PM +0900, Tetsuo Handa wrote: > > [ 272.851035] Showing busy workqueues and worker pools: > > [ 272.852583] workqueue events: flags=0x0 > > [ 272.853942] pwq 6: cpus=3 node=0 flags=0x0 nice=0 active=1/256 > > [ 272.855781] pending: vmw_fb_dirty_flush [vmwgfx] > > [ 272.857500] pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256 > > [ 272.859359] pending: vmpressure_work_fn > > [ 272.860840] workqueue events_freezable_power_: flags=0x84 > > [ 272.862461] pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=2/256 > > [ 272.864479] in-flight: 11286:disk_events_workfn > > What's this guy doing? Can you get stack dump on 11286 (or whatever > is in flight in the next lockup)? Wait, this series doesn't include Tetsuo's change. Of course it won't fix the deadlock problem. What's necessary is Tetsuo's patch + WQ_MEM_RECLAIM. Thanks. -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>