On Wed, Aug 21, 2019 at 03:20:21PM +0200, David Sterba wrote: > On Tue, Aug 13, 2019 at 10:33:42AM -0700, Omar Sandoval wrote: > > From: Omar Sandoval <osan...@fb.com> > > > > This does some cleanups to the Btrfs workqueue code following my > > previous fix [1]. Changed since v1 [2]: > > > > - Removed errant Fixes: tag in patch 1 > > - Fixed a comment typo in patch 2 > > - Added NB: to comments in patch 2 > > - Added Nikolay and Filipe's reviewed-by tags > > > > Thanks! > > > > 1: > > https://lore.kernel.org/linux-btrfs/0bea516a54b26e4e1c42e6fe47548cb48cc4172b.1565112813.git.osan...@fb.com/ > > 2: https://lore.kernel.org/linux-btrfs/cover.1565680721.git.osan...@fb.com/ > > > > Omar Sandoval (2): > > Btrfs: get rid of unique workqueue helper functions > > Btrfs: get rid of pointless wtag variable in async-thread.c > > The patches seem to cause crashes inside the worques, happend several > times in random patches, sample stacktrace below. This blocks me from > testing so I'll move the patches out of misc-next for now and add back > once there's a fix.
Another possibility is that the cleanup patches make it more likely to happen and the root cause is "Btrfs: fix workqueue deadlock on dependent filesystems".