Hi, I'm currently fuzzing rev 2076992 and things start to slowly, slowly quiet down. We will probably run out of steam at the end of the week when a total of (roughly) half a billion BTRFS-images have passed by. I will switch revisions to current HEAD and restart the whole process then. A few things:
* There are a couple of crashes (mostly segfaults) I have not reported yet. I'll report them if they show up again with the latest revision. * The coverage-analysis shows assertion failures which are currently silenced. An assertion failure is technically a worse disaster successfully prevented, it still constitutes unexpected/unusable behaviour, though. Do you want assertions to be enabled and images triggering those assertions reported? This is basically the same conundrum as with BUG_ON and abort(). * A few endless loops entered into by btrfsck are currently unmitigated (see bugs 155621, 155571, 155551 and 155151). It would be nice if those had been taken care of by next week if possible. Best regards Lukas -- 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
