Re: [PATCH v2] ext4: Fix a BUG in mb_mark_used during trim.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Christoph,
On 03/03/2011 10:11 PM, Christoph Hellwig wrote:
On Thu, Mar 03, 2011 at 09:59:34PM +0800, Tao Ma wrote:
From: Tao Ma<boyu.mt@xxxxxxxxxx>

In a bs=4096 volume, if we call FITRIM with the following parameter as
fstrim_range(start = 102400, len = 134144000, minlen = 10240),
Can you add a xfstests regression test for this particular invocation?
We already have Lukas' fstrim.c tester in the tree, so it could be a
simple wrapper around it.
Actually these numbers are related to the block size of a ext4 volume.
To be more specific, with the above number, we have
first_block + block_len > EXT4_BLOCKS_PER_GROUP while
block_len < EXT4_BLOCKS_PER_GROUP.
So do you think it is generic enough for a test case in xfstests since now this
tool kit is also used to test xfs and btrfs?

Regards,
Tao




--
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


[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux