Hide Forgot
Description of problem: xfstests 260 fails on ext4 FSTYP -- ext4 PLATFORM -- Linux/x86_64 fstest 2.6.32-212.el6.x86_64 MKFS_OPTIONS -- lazy_itable_init /dev/sdb2 MOUNT_OPTIONS -- -o acl,user_xattr -o context=system_u:object_r:nfs_t:s0 /dev/sdb2 /mnt/testarea/scratch 260 [failed, exit status 1] - output mismatch (see 260.out.bad) --- 260.out 2011-10-20 19:11:39.000000000 +0800 +++ 260.out.bad 2011-10-27 18:53:53.931268221 +0800 @@ -11,4 +11,5 @@ [+] Default length with start set (should succeed) [+] Length beyond the end of fs (should succeed) [+] Length beyond the end of fs with start set (should succeed) +It seems that fs logic handling start argument overflows Test done I used -E lazy_itable_init mkfs option here to make sure it's not introduced by bug 696559. This is not a regression, 6.1 GA kernel fails too Version-Release number of selected component (if applicable): kernel-2.6.32-212.el6 How reproducible: 100% Steps to Reproduce: 1. prepare two partitions on SSD which supports TRIM(lvm over SSD won't work) 2. check 260 3. Actual results: test fail Expected results: test pass Additional info:
Lukas, mind taking this one?
Oh, they have used xfstest I have written just recently to find exactly this bug upstream, who would have thought of that ?:) Yes, I'll take it. The change is not upstream yet (due to bigalloc changes).
Yep, xfstests can be fun that way. :)
Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
*** This bug has been marked as a duplicate of bug 767219 ***