On Mon, Aug 29, 2016 at 08:47:10PM +0200, Lukas Lueg wrote: > I'll report new issues to bz as they turn up from the current round > only if they represent a yet unreported kind of problem (e.g. there > are stack-based buffer over- and underruns lurking, I lost them due to > a bug in my setup, though). The next round will be much faster as I've > now vastly improved my automatic bug triage and fuzzing speed. > > I lost interest once after bugs went unanswered - there are bugs still > open and unanswered from 2015/04. I hope this won't be a problem this > time. Yeah, the lack if replies is unfortunate and happens. There's a disproportion between number of people who report bugs and who go through them and fix. I personally look out for the fuzzing bugs as they usually come with an image and it's easy to create a testcase from them, reproducible bugs also tend to get fixes faster. I must have missed the bugs though, there are 3 fuzzed images, reported by you in bugs 96971, 97191 and 97271. I see two more (97031 and 97021) and will look into them. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
