1. add one space between # and test description 2. remove creator/owner info 3. fix common/rc and common/filter path so they can be sourced correctly 4. no need to remove $seq.full cause it's not use
Hi Eryu, Thanks for this cleanup patch. I was going to revert patch "bbaf78c0" which introduced test generic/310 but will wait and see if Zhao will provide more information which could be added to th
Make sense, thanks for the review. I didn't look into the test deeply but I found the test seems to run for hours on my 3.9-rc4 test box, not sure what goes wrong here. Thanks, Eryu
When I ran it on ext2, ext3 and ext4 which has dir_index feature disabled, I got something like this: EXT3-fs error (device loop1): ext3_readdir: bad entry in directory #34817: rec_len is \ smaller t
So what is the criteria for a test failure? The test body is only reading from the filesystem, so a ro,remount won't cause an obvious failure of the test. Perhaps the test should have more comments i
There haven't a obvious criteria for a test failure, you should see it from dmesg while you run the test. Yes, i'll add more comments to explain it! Thanks, Zhao Hongjiang
Which means for most cases (i.e. automated test harnesses), a test failure will go unnoticed. The test *must* detect failures if it is to be useful as a regression test. That's the whole point of a r