Re: panic: ext2fs_dirbadentry

2013-07-20 Thread Ted Unangst
On Wed, Jul 17, 2013 at 12:11, Sergey Bronnikov wrote: Bug was catched by fsfuzzer. Probably that bug cannot be found in real life with real usecase, but anyway it is a bug. Sorry, but I don't think these bugs are interesting. The filesystem code panics when it encounters a broken filesystem.

Re: panic: ext2fs_dirbadentry

2013-07-20 Thread Theo de Raadt
On Wed, Jul 17, 2013 at 12:11, Sergey Bronnikov wrote: Bug was catched by fsfuzzer. Probably that bug cannot be found in real life with real usecase, but anyway it is a bug. Sorry, but I don't think these bugs are interesting. The filesystem code panics when it encounters a broken

Re: panic: ext2fs_dirbadentry

2013-07-19 Thread Sergey Bronnikov
On 09:50 Wed 17 Jul , Philip Guenther wrote: On Wed, 17 Jul 2013, Sergey Bronnikov wrote: Bug was catched by fsfuzzer. Probably that bug cannot be found in real life with real usecase, but anyway it is a bug. Is e2fsck being run (forced?) after fuzzing and before trying to mount it?

panic: ext2fs_dirbadentry

2013-07-17 Thread Sergey Bronnikov
Bug was catched by fsfuzzer. Probably that bug cannot be found in real life with real usecase, but anyway it is a bug. panic: ext2fs_dirbadentry Stopped at Debugger+0x5: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING

Re: panic: ext2fs_dirbadentry

2013-07-17 Thread Kenneth R Westerback
this consistency check indicates a bug in the code? Since fsfuzzer is supposed to create logs and allow reproducible tests, sharing those logs and directions on reproducing the failure would also be nice. Ken panic: ext2fs_dirbadentry Stopped atDebugger+0x5: leave RUN AT LEAST 'trace

Re: panic: ext2fs_dirbadentry

2013-07-17 Thread Sergey Bronnikov
On 09:50 Wed 17 Jul , Philip Guenther wrote: On Wed, 17 Jul 2013, Sergey Bronnikov wrote: Bug was catched by fsfuzzer. Probably that bug cannot be found in real life with real usecase, but anyway it is a bug. Is e2fsck being run (forced?) after fuzzing and before trying to mount it? No.