Eric Sandeen wrote: > Eric Sesterhenn / Snakebyte wrote: >> hi, >> >> after fsfuzz >> (http://www.securityfocus.com/archive/1/449568/30/0/threaded) was >> released i decided to give it a spin. So far I got two problematic >> images: >> >> http://www.cobra-basket.de/ext3_ls_prozzy_hog.img.bz2 >> which makes the kernel use as much cpu as it can get >> >> http://www.cobra-basket.de/ext3_memhog.img.bz2 >> eats all memory it can get Works for me w/ that patch: [root@link-07 ~]# mount -o loop ext3_ls_prozzy_hog.img mnt/ [root@link-07 ~]# ls mnt/ [root@link-07 ~]# dmesg | tail -n 6 EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs error (device loop0): htree_dirblock_to_tree: bad entry in directory #2: rec_len % 4 != 0 - offset=24, inode=11, rec_len=989, name_len=10 Aborting journal on device loop0. ext3_abort called. EXT3-fs error (device loop0): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only [root@link-07 ~]# mount -o loop ext3_memhog.img mnt/ [root@link-07 ~]# ls mnt [root@link-07 ~]# dmesg | tail -n 6 EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs error (device loop0): htree_dirblock_to_tree: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=75, rec_len=0, name_len=0 Aborting journal on device loop0. ext3_abort called. EXT3-fs error (device loop0): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only -Eric - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
