Re: Fwd: State of the fuzzer

2016-11-02 Thread David Sterba
Hi, On Tue, Oct 11, 2016 at 02:07:48PM +0200, Lukas Lueg wrote: > I've now shut down all fuzzer nodes since they only cost money and > there is no progress on most of the aforementioned bugs. sorry, I didn't know there are cost implications. I've triaged the bugs some time ago and tried to fix

Fwd: State of the fuzzer

2016-10-11 Thread Lukas Lueg
Hi, I've now shut down all fuzzer nodes since they only cost money and there is no progress on most of the aforementioned bugs. Best regards Lukas -- Forwarded message -- From: Lukas Lueg <lukas.l...@gmail.com> Date: 2016-09-26 11:39 GMT+02:00 Subject: Re: State of the

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

State of the fuzzer

2016-09-06 Thread Lukas Lueg
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