* Eric Sesterhenn (snakebyte@xxxxxx) wrote: > hi, > > while running a modified version of fsfuzzer i triggered the BUG() in > ext4_mb_release_inode_pa(). Sadly I am not able to reproduce this using > the generated image, but running the fuzzer will usually trigger this in > less than 40 attempts. Increasing the JBD2 Debug level didnt give more > information. The kernel is current git with > ext4-fix-null-pointer-deref-in-journal_wait_on_commit_record.patch > applied. I am now able to reproduce this using this image: http://www.cccmz.de/~snakebyte/ext4.24.img.bz2 the following commands will trigger the oops for me mount cfs/ext4.24.img /media/test -t ext4dev -o extents -o loop mkdir /media/test/stress chown snakebyte:snakebyte /media/test/stress && sudo -u snakebyte fstest -n 10 -l 10 -f 5 -s 40000 -p /media/test/stress/ The && between the chown and fstest seems necessary Greetings, 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
