Hello Marc, Friday, November 24, 2017, 2:41:12 PM, you wrote: > I have bcache | dmcrypt | btrfs, and I was upgrading to 4.14.0 when > someone told me about the corruption problems people noticed in 4.14.0 > Is there an understood root cause and something to avoid to not trigger > the bug, or not so much? The bug was caused by a change in the block layer code (outside of bcache), commit 74d46992e0d9dee7f1f376de0d56d31614c8a17a, "block: replace bi_bdev with a gendisk pointer and partitions index". I don't know if there are any specific usage patterns that trigger the problem. I strongly suggest not to run the affected kernel versions on any machine that uses bcache (or, even better, on any machine at all). > I saw a bunch of patches go by and I'm not too clear if 4.14.1 is safe, > or not. In 4.14.1 (as published here https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tag/?h=v4.14.1), this bug was not fixed yet. However, the very recent 4.14.2 does contain the fix (commit 62530ed8b1d07a45dec94d46e521c0c6c2d476e6, "bio: ensure __bio_clone_fast copies bi_partno"). > Can someone advise? > Thanks, > Marc Pavel Goran -- 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
