On Sun, Feb 21, 2016 at 09:36:44AM +0800, Qu Wenruo wrote: > > > On 02/19/2016 09:41 PM, Anand Jain wrote: > > > > > > Saw below warn leading to bug when running btrfs/011, not > > reproducible. Any idea ? > > > Seems like another wq_destroy race. > > But it's hard to locate which wq is the cause from backtrace only.
Name of the workqueue is in the first stacktrasce, it's readahead. The crash happens in 'umount'. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
