Eric Wheeler writes: > Try the patch below, this is the only deadlock fix that isn't upstream > that I'm aware of. Your trace above doesn't indicate any bcache > functions, so this could be hard to troubleshoot. Thanks for the suggestion, but I think I've found the real cause. I wasn't able to reproduce with 4.11.1, which I suspect is due to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/nvme/host/core.c?h=v4.11.1&id=302ad8cc09339ea261eef58a8d5f4a116a8ffda5 which fixes an issue that matches the symptoms I've seen. The history of that change is http://lists.infradead.org/pipermail/linux-nvme/2017-March/008593.html https://patchwork.kernel.org/patch/9589187/ http://lists.infradead.org/pipermail/linux-nvme/2017-January/007617.html FWIW I was not able to reproduce with a filesystem directly on an nvme partition, but I guess stacked devices or bcache changed things enough to trigger. -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
