Re: State of the fuzzer

2016-09-26 Thread Lukas Lueg
Hi David, do we have any chance of engagement on those 23 bugs which came out of the last fuzzing round? The nodes have been basically idle for a week, spewing duplicates and variants of what's already known... Best regards Lukas 2016-09-20 13:33 GMT+02:00 Lukas Lueg : > There are now 21 bugs op

Re: State of the fuzzer

2016-09-20 Thread Lukas Lueg
There are now 21 bugs open on bko, most of them crashes and some undefined behavior. The nodes are now mostly running idle as no new paths are discovered (after around one billion images tested in the current run). My thoughts are to wait until the current bugs have been fixed, then restart the wh

Re: State of the fuzzer

2016-09-13 Thread Lukas Lueg
I've booted another instance with btrfs-progs checked out to 2b7c507 and collected some bugs which remained from the run before the current one. The current run discovered what qgroups are just three days ago and will spend some time on that. I've also added UBSAN- and MSAN-logging to my setup and

Re: State of the fuzzer

2016-09-09 Thread David Sterba
On Tue, Sep 06, 2016 at 10:32:28PM +0200, Lukas Lueg wrote: > 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