On 21.02.2018 19:18, Christoph Anton Mitterer wrote: > e8f1bc1493855e32b7a2a019decc3c353d94daf6 > > That bug... When was that introduced and how can I find out whether an fs was > affected/corrupted by this? Cause I've mounted and wrote to some extremely > important (to me) fs recently.
The bug that this patch solves is unlikely to lead to fs-wide corruption or indeed, any corruption at all. At mostit might make you deref a null pointer and cause a crash - the first thing you reported. The follow up reports don't really correspond to it. The bug was introduced in 4.7 kernel (as evident from the stable tag on the patch) > > Thanks, Chris. > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
